feat: add config-driven scaffolds and managed feature updates (#10)

Author: Ali-dev11

CHANGELOG.md

@@ -6,6 +6,27 @@ The format follows Keep a Changelog and the version numbers follow Semantic Vers
 
 ## [Unreleased]
 
+## [0.4.5] - 2026-03-31
+
+### Added
+
+- Added config-as-code support with `devforge init --config <path>` so saved scaffold plans can be replayed non-interactively.
+- Added `devforge init --save-config [path]` so interactive runs can emit a reusable `devforge.config.json` file for teams and future scaffolds.
+- Added config regression coverage that round-trips normalized plans through saved config files and verifies scaffold output stays deterministic.
+- Added `devforge add <feature>` for managed post-scaffold updates, with initial support for `testing`, `docker`, `github-actions`, and `ai-rules`.
+
+### Changed
+
+- Extended CLI help, generated project docs, and repository docs to explain the new config-driven workflow and how reusable scaffold plans fit alongside interactive prompts.
+- Routed config-driven runs through the same environment defaults and normalization flow as interactive runs so support-matrix rules stay consistent across both entrypoints.
+- Extended the packed npm-artifact smoke path so it now exercises `devforge add docker` after scaffold creation, verifying the shipped CLI can perform managed post-scaffold updates.
+
+### Fixed
+
+- Made post-scaffold feature application metadata-driven by reading `.devforge/project-plan.json`, which avoids stack guessing and keeps repeated `devforge add` runs idempotent.
+- Fixed `devforge init --save-config` with the default in-project config path so the saved config no longer makes the target directory look non-empty before generation.
+- Tightened `devforge add` guidance and managed-file updates so repeated runs avoid unnecessary churn and generated README content stays aligned with newly added managed features.
+
 ## [0.4.4] - 2026-03-31
 
 ### Added

README.md

@@ -45,12 +45,25 @@ Machine readiness check:
 npx --yes @ali-dev11/devforge@latest doctor
 ```
 
+Add managed features later:
+
+```bash
+npx --yes @ali-dev11/devforge@latest add testing
+npx --yes @ali-dev11/devforge@latest add docker
+```
+
 Plan-only preflight:
 
 ```bash
 npx --yes @ali-dev11/devforge@latest init --preflight-only
 ```
 
+Config-driven scaffold:
+
+```bash
+npx --yes @ali-dev11/devforge@latest init --config ./devforge.config.json --output ./my-app
+```
+
 ## What The CLI Asks You
 
 DevForge keeps core setup decisions required, and pushes the rest behind optional customization steps.
@@ -119,6 +132,21 @@ npm run runtime:matrix -- --scenario backend-hono --scenario cli-tool
 - `npm run smoke:packed` packs the actual npm tarball, installs it into a temp directory, and verifies the published artifact shape instead of only the source checkout.
 - `npm run runtime:matrix -- --scenario ...` installs, builds, and verifies generated projects so the scaffold output is tested as a product, not just as source code.
 
+## Config As Code
+
+- `devforge init --save-config` saves the resolved scaffold plan as `devforge.config.json` in the generated project by default.
+- `devforge init --save-config ./configs/web.json` saves the normalized plan to a custom location.
+- `devforge init --config ./devforge.config.json --output ./my-app` replays a saved scaffold non-interactively.
+- `--output` and `--name` can still override the saved config at runtime, so the same config file stays reusable across multiple projects.
+
+## Add Features Later
+
+- `devforge add testing` enables the scaffold's recommended test runner for the saved stack and writes the matching test config and starter tests.
+- `devforge add docker` adds the generated `Dockerfile` and `.dockerignore` for the current DevForge project.
+- `devforge add github-actions` adds the generated CI workflow for the current project stack.
+- `devforge add ai-rules` restores `AGENTS.md`, `.cursor`, `.claude`, and the AI rule source docs when those were skipped initially.
+- `devforge add` works only inside DevForge-generated projects because it reads `.devforge/project-plan.json` to update managed files safely.
+
 ## Repository Docs
 
 - [Documentation Site](https://ali-dev11.github.io/devforge/)

docs/changelog.md

@@ -9,6 +9,27 @@ Track what changed in DevForge CLI across releases, including scaffolding behavi
 - [GitHub Releases](https://github.com/Ali-dev11/devforge/releases)
 - [Repository Changelog](https://github.com/Ali-dev11/devforge/blob/main/CHANGELOG.md)
 
+## [0.4.5] - 2026-03-31
+
+### Added
+
+- Added config-as-code support with `devforge init --config <path>` so saved scaffold plans can be replayed non-interactively.
+- Added `devforge init --save-config [path]` so interactive runs can emit a reusable `devforge.config.json` file for teams and future scaffolds.
+- Added config regression coverage that round-trips normalized plans through saved config files and verifies scaffold output stays deterministic.
+- Added `devforge add <feature>` for managed post-scaffold updates, with initial support for `testing`, `docker`, `github-actions`, and `ai-rules`.
+
+### Changed
+
+- Extended CLI help, generated project docs, and repository docs to explain the new config-driven workflow and how reusable scaffold plans fit alongside interactive prompts.
+- Routed config-driven runs through the same environment defaults and normalization flow as interactive runs so support-matrix rules stay consistent across both entrypoints.
+- Extended the packed npm-artifact smoke path so it now exercises `devforge add docker` after scaffold creation, verifying the shipped CLI can perform managed post-scaffold updates.
+
+### Fixed
+
+- Made post-scaffold feature application metadata-driven by reading `.devforge/project-plan.json`, which avoids stack guessing and keeps repeated `devforge add` runs idempotent.
+- Fixed `devforge init --save-config` with the default in-project config path so the saved config no longer makes the target directory look non-empty before generation.
+- Tightened `devforge add` guidance and managed-file updates so repeated runs avoid unnecessary churn and generated README content stays aligned with newly added managed features.
+
 ## [0.4.4] - 2026-03-31
 
 ### Added

docs/development.md

@@ -18,6 +18,19 @@ npm run check
 npx --yes @ali-dev11/devforge@latest doctor
 ```
 
+## Config-As-Code Workflow
+
+```bash
+npx --yes @ali-dev11/devforge@latest init --yes --save-config
+npx --yes @ali-dev11/devforge@latest init --config ./devforge.config.json --output ./my-app
+npx --yes @ali-dev11/devforge@latest add testing
+```
+
+- `--save-config` writes the normalized project plan to `devforge.config.json` so the same scaffold can be replayed later.
+- `--config` runs the generator non-interactively from a saved plan while still letting `--output` or `--name` override the destination.
+- Config-driven runs pass through the same normalization and compatibility checks as interactive runs, so invalid hand-written combinations are still corrected or rejected with guidance.
+- `devforge add <feature>` updates an existing DevForge project by reading `.devforge/project-plan.json` and rewriting only the managed files for that feature.
+
 ## Repository Commands
 
 ```bash
@@ -51,6 +64,9 @@ npm run runtime:matrix -- --scenario backend-hono --scenario cli-tool
 
 - Prefer `npm run smoke` for quick CLI sanity checks.
 - Run `npx --yes @ali-dev11/devforge@latest init --preflight-only` when you want stack-aware readiness checks without writing a new project yet.
+- Use `npx --yes @ali-dev11/devforge@latest init --save-config` when you want an interactive run to become a reusable team preset later.
+- Use `npx --yes @ali-dev11/devforge@latest init --config ./devforge.config.json --output ./my-app` when validating reproducible scaffold output.
+- Use `npx --yes @ali-dev11/devforge@latest add testing`, `add docker`, `add github-actions`, or `add ai-rules` when validating managed post-scaffold updates.
 - Use `npm run runtime:matrix` when changing templates, prompts, package-manager behavior, or generated runtime surfaces.
 - Use `npm run smoke:packed` when changing the package entrypoints, published files, CLI dispatch, or install-time behavior.
 - If you touch microfrontend templates, validate the generated `dev` workflow, not just build output.

docs/index.md

@@ -35,6 +35,12 @@ DevForge CLI turns project intent into a runnable JavaScript or TypeScript repos
 - `npx --yes @ali-dev11/devforge@latest`: run DevForge without a global install.
 - `npx --yes @ali-dev11/devforge@latest doctor`: inspect local machine readiness before generating a scaffold.
 - `npx --yes @ali-dev11/devforge@latest init --preflight-only`: run stack-aware checks for the chosen plan without writing files yet.
+- `npx --yes @ali-dev11/devforge@latest init --save-config`: save the resolved scaffold plan as `devforge.config.json` for reuse.
+- `npx --yes @ali-dev11/devforge@latest init --config ./devforge.config.json --output ./my-app`: regenerate a saved scaffold non-interactively in a new location.
+- `npx --yes @ali-dev11/devforge@latest add testing`: add the recommended managed testing setup to an existing DevForge project.
+- `npx --yes @ali-dev11/devforge@latest add docker`: add the generated Docker assets to an existing DevForge project.
+- `npx --yes @ali-dev11/devforge@latest add github-actions`: add the generated CI workflow to an existing DevForge project.
+- `npx --yes @ali-dev11/devforge@latest add ai-rules`: add the managed AI rule files back into an existing DevForge project.
 - `Project prompts`: use the [Prompt Reference](./prompts.md) when you want to know what a question changes before answering it.
 - `npm run check`: validate the DevForge repository itself before pushing changes.
 - `npm run smoke`: verify a non-interactive scaffold path.

package-lock.json

@@ -1,6 +1,6 @@
 {
   "name": "@ali-dev11/devforge",
-  "version": "0.4.4",
+  "version": "0.4.5",
   "description": "Production-focused AI-native project scaffolding CLI for JavaScript and TypeScript teams.",
   "license": "MIT",
   "author": "Ali-dev11",

package.json

@@ -1,4 +1,4 @@
-import { mkdirSync, mkdtempSync, readdirSync, rmSync } from "node:fs";
+import { existsSync, mkdirSync, mkdtempSync, readdirSync, rmSync } from "node:fs";
 import { tmpdir } from "node:os";
 import { join, resolve } from "node:path";
 import { spawnSync } from "node:child_process";
@@ -70,12 +70,31 @@ try {
       resolve(installDir, "node_modules/@ali-dev11/devforge/dist/bin/devforge.js"),
       "init",
       "--yes",
+      "--save-config",
       "--skip-install",
       "--output",
       outputDir,
     ],
     rootDir,
   );
+
+  run(
+    "node",
+    [
+      resolve(installDir, "node_modules/@ali-dev11/devforge/dist/bin/devforge.js"),
+      "add",
+      "docker",
+    ],
+    outputDir,
+  );
+
+  if (!existsSync(resolve(outputDir, "devforge.config.json"))) {
+    throw new Error("Packed smoke run did not create devforge.config.json during `devforge init --save-config`.");
+  }
+
+  if (!existsSync(resolve(outputDir, "Dockerfile"))) {
+    throw new Error("Packed smoke run did not create Dockerfile after `devforge add docker`.");
+  }
 } finally {
   rmSync(workspace, { recursive: true, force: true });
 }

scripts/smoke-packed.mjs

@@ -1,4 +1,5 @@
 import type { CliOptions } from "./types.js";
+import { runAddCommand } from "./commands/add.js";
 import { runDoctorCommand } from "./commands/doctor.js";
 import { runInitCommand } from "./commands/init.js";
 import { DEVFORGE_VERSION } from "./version.js";
@@ -13,18 +14,36 @@ function readFlagValue(flag: string, args: string[]): string {
   return value;
 }
 
+function readOptionalFlagValue(args: string[]): string | undefined {
+  const value = args[0];
+
+  if (!value || value.startsWith("-")) {
+    return undefined;
+  }
+
+  args.shift();
+  return value;
+}
+
 function assertInitOnlyFlag(currentCommand: CliOptions["command"], flag: string): void {
   if (currentCommand !== "init") {
     throw new Error(`${flag} can only be used with \`devforge init\`.`);
   }
 }
 
+function assertInitOrAddFlag(currentCommand: CliOptions["command"], flag: string): void {
+  if (currentCommand !== "init" && currentCommand !== "add") {
+    throw new Error(`${flag} can only be used with \`devforge init\` or \`devforge add\`.`);
+  }
+}
+
 export function parseArgs(argv: string[]): CliOptions {
   const options: CliOptions = {
     command: "init",
     resume: false,
     skipInstall: false,
     preflightOnly: false,
+    saveConfig: false,
     yes: false,
   };
 
@@ -44,8 +63,21 @@ export function parseArgs(argv: string[]): CliOptions {
   if (firstArg === "doctor") {
     options.command = "doctor";
     args.shift();
-  } else
-  if (firstArg === "init") {
+  } else if (firstArg === "add") {
+    options.command = "add";
+    args.shift();
+    if (args[0] === "--help" || args[0] === "-h") {
+      options.command = "help";
+      return options;
+    }
+    const feature = args.shift();
+
+    if (!feature || feature.startsWith("-")) {
+      throw new Error("Missing feature for `devforge add`. Expected one of: testing, docker, github-actions, ai-rules.");
+    }
+
+    options.addFeature = feature as CliOptions["addFeature"];
+  } else if (firstArg === "init") {
     args.shift();
   } else if (firstArg && !firstArg.startsWith("-")) {
     throw new Error(`Unknown command: ${firstArg}`);
@@ -68,13 +100,22 @@ export function parseArgs(argv: string[]): CliOptions {
         options.command = "version";
         return options;
       case "--skip-install":
-        assertInitOnlyFlag(options.command, "--skip-install");
+        assertInitOrAddFlag(options.command, "--skip-install");
         options.skipInstall = true;
         break;
       case "--preflight-only":
         assertInitOnlyFlag(options.command, "--preflight-only");
         options.preflightOnly = true;
         break;
+      case "--config":
+        assertInitOnlyFlag(options.command, "--config");
+        options.configPath = readFlagValue("--config", args);
+        break;
+      case "--save-config":
+        assertInitOnlyFlag(options.command, "--save-config");
+        options.saveConfig = true;
+        options.saveConfigPath = readOptionalFlagValue(args);
+        break;
       case "--yes":
       case "-y":
         assertInitOnlyFlag(options.command, "--yes");
@@ -97,6 +138,10 @@ export function parseArgs(argv: string[]): CliOptions {
     }
   }
 
+  if (options.resume && options.configPath) {
+    throw new Error("`--resume` cannot be used together with `--config`.");
+  }
+
   return options;
 }
 
@@ -107,17 +152,22 @@ Usage:
   devforge
   devforge init
   devforge init --resume
+  devforge init --config ./devforge.config.json
+  devforge add testing
   devforge doctor
 
 Commands:
   init            Start a new scaffold session
+  add             Add a managed feature to an existing DevForge project
   doctor          Inspect local machine readiness for DevForge scaffolds
   help            Show command help
   version         Print the current CLI version
 
 Flags:
   --resume         Resume the last saved init session
-  --skip-install   Generate files without installing dependencies
+  --config <path>  Load a saved DevForge config and run non-interactively
+  --save-config    Save the resolved scaffold plan as devforge.config.json
+  --skip-install   Generate or update files without installing dependencies
   --preflight-only Stop after printing stack-aware readiness checks
   --yes, -y        Use defaults without prompts
   --output <dir>   Write the generated project to a custom directory
@@ -128,7 +178,11 @@ Flags:
 Examples:
   npx @ali-dev11/devforge@latest
   npx @ali-dev11/devforge@latest doctor
+  npx @ali-dev11/devforge@latest init --config ./devforge.config.json --output ./my-app
+  npx @ali-dev11/devforge@latest init --yes --save-config
+  npx @ali-dev11/devforge@latest add docker
   npx @ali-dev11/devforge@latest init --yes --skip-install --output ./my-app
+  devforge add testing --skip-install
   devforge init --preflight-only
   devforge init --resume
 `);
@@ -156,5 +210,10 @@ export async function runCli(argv = process.argv.slice(2)): Promise<void> {
     return;
   }
 
+  if (options.command === "add") {
+    await runAddCommand(options);
+    return;
+  }
+
   await runInitCommand(options);
 }