feat-forge 1.1.0 → 1.2.3

package/README.md

@@ -10,11 +10,11 @@
 
 Its goal is to make the specification of features explicit and separate the thinking/specifying phase from the coding/implementation phase, across multiple agents and repositories, while keeping everything organized and traceable.
 
-With **FeatForge** you will be able to :
+With **FeatForge** you will be able to:
 
 - Parallelize work on multiple features:
     - across multiple repositories.
-    - accross multiple agents.
+    - across multiple agents.
     - while keeping track of everything.
 - Come back to any feature after days/weeks and immediately understand its initial specifications.
 - Change agent configurations and prompts on a per-feature basis.
@@ -26,7 +26,7 @@ With **FeatForge** you will be able to :
 - Not opinionated about how you specify features, how you implement them, or how you use agents. It just provides a structure (yet customizable) and a workflow to keep everything organized and traceable.
 - Partially tested with : Copilot, Codex, Claude code (+Ollama, LM-Studio). But it should work with any agent that can be configured to read/write files in the `.active-spec` folders.
 
-**_This is an expirement, trying to mix between classic development and vibe-coding in large project with quality and sustainability in mind by making specification explicit and separating thinking from coding accross multiple agents and repositories._**
+**_This is an experiment, trying to mix between classic development and vibe-coding in large project with quality and sustainability in mind by making specification explicit and separating thinking from coding across multiple agents and repositories._**
 
 ## Key Concepts
 
@@ -43,7 +43,7 @@ With **FeatForge** you will be able to :
 ## Installation
 
 ```bash
-npm install -g feat-forge-cli
+npm install -g feat-forge
 forge --version
 ```
 
@@ -116,7 +116,7 @@ forge-project-root/
 ## Modes
 
 Each branch has a mode stored in `.specs/<slug>/.forge-mode`. Switching modes updates agent adapter files with the corresponding templates.
-Agent name are useful when calling subagent
+Agent names are useful when calling subagents.
 
 Built-in modes:
 
@@ -302,6 +302,23 @@ Refresh agent adapter files for the nearest branch.
 
 Scan repositories for service declarations and generate configuration with allocated ports.
 
+Service declarations are read from `.forge/services.json` in each repository. You can define an optional dedicated health endpoint per service:
+
+```json
+{
+  "services": [
+    {
+      "name": "api",
+      "type": "http",
+      "path": "/api",
+      "healthCheckPath": "/health"
+    }
+  ]
+}
+```
+
+If `healthCheckPath` is omitted, proxy health checks fallback to `path`, then `/`.
+
 ---
 
 ### `forge services list [branch]`
@@ -355,6 +372,10 @@ For all commands and options:
 forge --help
 ```
 
+## Contributing
+
+See [CONTRIBUTING.md](./CONTRIBUTING.md) for development setup and contribution workflow.
+
 # License
 
 [![License: AGPL-3.0](https://img.shields.io/npm/l/feat-forge)](./LICENSE)

package/dist/commands/CompletionCommands.js

@@ -176,18 +176,10 @@ try{
         const envCommands = data.envCmd?.subcommands.map((cmd) => cmd.name).join(' ') || '';
         const maintenanceCommands = data.maintenanceCmd?.subcommands.map((cmd) => cmd.name).join(' ') || '';
         const agentCommands = data.agentCmd?.subcommands.map((cmd) => cmd.name).join(' ') || '';
-        const featureSlugCmds = data.featureCmd?.subcommands
-            .filter((cmd) => data.slugSubcommands.includes(cmd.name))
-            .map((cmd) => cmd.name) || [];
-        const fixSlugCmds = data.fixCmd?.subcommands
-            .filter((cmd) => data.slugSubcommands.includes(cmd.name))
-            .map((cmd) => cmd.name) || [];
-        const releaseSlugCmds = data.releaseCmd?.subcommands
-            .filter((cmd) => data.slugSubcommands.includes(cmd.name))
-            .map((cmd) => cmd.name) || [];
-        const mainSlugCmds = data.mainCommands
-            .filter((cmd) => data.rootSlugCommands.includes(cmd.name))
-            .map((cmd) => cmd.name);
+        const featureSlugCmds = data.featureCmd?.subcommands.filter((cmd) => data.slugSubcommands.includes(cmd.name)).map((cmd) => cmd.name) || [];
+        const fixSlugCmds = data.fixCmd?.subcommands.filter((cmd) => data.slugSubcommands.includes(cmd.name)).map((cmd) => cmd.name) || [];
+        const releaseSlugCmds = data.releaseCmd?.subcommands.filter((cmd) => data.slugSubcommands.includes(cmd.name)).map((cmd) => cmd.name) || [];
+        const mainSlugCmds = data.mainCommands.filter((cmd) => data.rootSlugCommands.includes(cmd.name)).map((cmd) => cmd.name);
         const featureSlugCase = featureSlugCmds.length > 0
             ? `                ${featureSlugCmds.join('|')})
                     if [[ \${cword} -eq 3 ]]; then
@@ -464,26 +456,22 @@ complete -F _forge_completion forge
     // ============================================================================
     generateZshCompletion() {
         const data = this.getCompletionData();
-        const commandsArray = data.mainCommands.map((cmd) => `        '${cmd.name}:${cmd.description.replace(/'/g, "''")}'`).join('\n');
+        const commandsArray = data.mainCommands
+            .map((cmd) => `        '${cmd.name}:${cmd.description.replace(/'/g, "''")}'`)
+            .join('\n');
         const featureArray = data.featureCmd?.subcommands.map((cmd) => `        '${cmd.name}:${cmd.description.replace(/'/g, "''")}'`).join('\n') || '';
         const fixArray = data.fixCmd?.subcommands.map((cmd) => `        '${cmd.name}:${cmd.description.replace(/'/g, "''")}'`).join('\n') || '';
         const releaseArray = data.releaseCmd?.subcommands.map((cmd) => `        '${cmd.name}:${cmd.description.replace(/'/g, "''")}'`).join('\n') || '';
-        const servicesArray = data.servicesCmd?.subcommands.map((cmd) => `        '${cmd.name}:${cmd.description.replace(/'/g, "''")}'`).join('\n') || '';
+        const servicesArray = data.servicesCmd?.subcommands.map((cmd) => `        '${cmd.name}:${cmd.description.replace(/'/g, "''")}'`).join('\n') ||
+            '';
         const envArray = data.envCmd?.subcommands.map((cmd) => `        '${cmd.name}:${cmd.description.replace(/'/g, "''")}'`).join('\n') || '';
-        const maintenanceArray = data.maintenanceCmd?.subcommands.map((cmd) => `        '${cmd.name}:${cmd.description.replace(/'/g, "''")}'`).join('\n') || '';
+        const maintenanceArray = data.maintenanceCmd?.subcommands.map((cmd) => `        '${cmd.name}:${cmd.description.replace(/'/g, "''")}'`).join('\n') ||
+            '';
         const agentArray = data.agentCmd?.subcommands.map((cmd) => `        '${cmd.name}:${cmd.description.replace(/'/g, "''")}'`).join('\n') || '';
-        const featureSlugCmds = data.featureCmd?.subcommands
-            .filter((cmd) => data.slugSubcommands.includes(cmd.name))
-            .map((cmd) => cmd.name) || [];
-        const fixSlugCmds = data.fixCmd?.subcommands
-            .filter((cmd) => data.slugSubcommands.includes(cmd.name))
-            .map((cmd) => cmd.name) || [];
-        const releaseSlugCmds = data.releaseCmd?.subcommands
-            .filter((cmd) => data.slugSubcommands.includes(cmd.name))
-            .map((cmd) => cmd.name) || [];
-        const mainSlugCmds = data.mainCommands
-            .filter((cmd) => data.rootSlugCommands.includes(cmd.name))
-            .map((cmd) => cmd.name);
+        const featureSlugCmds = data.featureCmd?.subcommands.filter((cmd) => data.slugSubcommands.includes(cmd.name)).map((cmd) => cmd.name) || [];
+        const fixSlugCmds = data.fixCmd?.subcommands.filter((cmd) => data.slugSubcommands.includes(cmd.name)).map((cmd) => cmd.name) || [];
+        const releaseSlugCmds = data.releaseCmd?.subcommands.filter((cmd) => data.slugSubcommands.includes(cmd.name)).map((cmd) => cmd.name) || [];
+        const mainSlugCmds = data.mainCommands.filter((cmd) => data.rootSlugCommands.includes(cmd.name)).map((cmd) => cmd.name);
         const featureSlugCase = featureSlugCmds.length > 0
             ? `                        ${featureSlugCmds.join('|')})
                             local -a slugs
@@ -793,8 +781,7 @@ compdef _forge forge
         const fixSlugCompletions = genSlugCompletions('fix', data.fixCmd, '__forge_fix_slugs');
         const releaseSlugCompletions = genSlugCompletions('release', data.releaseCmd, '__forge_release_slugs');
         // Root-level slug commands
-        const mainSlugCmds = data.mainCommands
-            .filter((cmd) => data.rootSlugCommands.includes(cmd.name));
+        const mainSlugCmds = data.mainCommands.filter((cmd) => data.rootSlugCommands.includes(cmd.name));
         const mainSlugCompletions = mainSlugCmds
             .map((cmd) => `complete -c forge -n "__fish_seen_subcommand_from ${cmd.name}" -a "(__forge_all_branches)"`)
             .join('\n');
@@ -1001,18 +988,10 @@ complete -c forge -n "__fish_seen_subcommand_from alias" -a pwsh -d "Generate Po
         const envCommandsList = toPsArray(data.envCmd?.subcommands.map((cmd) => cmd.name) || []);
         const maintenanceCommandsList = toPsArray(data.maintenanceCmd?.subcommands.map((cmd) => cmd.name) || []);
         const agentCommandsList = toPsArray(data.agentCmd?.subcommands.map((cmd) => cmd.name) || []);
-        const featureSlugCommandsList = toPsArray(data.featureCmd?.subcommands
-            .filter((cmd) => data.slugSubcommands.includes(cmd.name))
-            .map((cmd) => cmd.name) || []);
-        const fixSlugCommandsList = toPsArray(data.fixCmd?.subcommands
-            .filter((cmd) => data.slugSubcommands.includes(cmd.name))
-            .map((cmd) => cmd.name) || []);
-        const releaseSlugCommandsList = toPsArray(data.releaseCmd?.subcommands
-            .filter((cmd) => data.slugSubcommands.includes(cmd.name))
-            .map((cmd) => cmd.name) || []);
-        const mainSlugCommandsList = toPsArray(data.mainCommands
-            .filter((cmd) => data.rootSlugCommands.includes(cmd.name))
-            .map((cmd) => cmd.name));
+        const featureSlugCommandsList = toPsArray(data.featureCmd?.subcommands.filter((cmd) => data.slugSubcommands.includes(cmd.name)).map((cmd) => cmd.name) || []);
+        const fixSlugCommandsList = toPsArray(data.fixCmd?.subcommands.filter((cmd) => data.slugSubcommands.includes(cmd.name)).map((cmd) => cmd.name) || []);
+        const releaseSlugCommandsList = toPsArray(data.releaseCmd?.subcommands.filter((cmd) => data.slugSubcommands.includes(cmd.name)).map((cmd) => cmd.name) || []);
+        const mainSlugCommandsList = toPsArray(data.mainCommands.filter((cmd) => data.rootSlugCommands.includes(cmd.name)).map((cmd) => cmd.name));
         const completionShellsList = toPsArray(['bash', 'zsh', 'fish', 'powershell', 'pwsh']);
         return `# forge PowerShell completion script
 

package/dist/foundation/PortAllocator.js

@@ -75,6 +75,8 @@ export class BranchPortAllocation {
         const serviceName = service.name;
         const existingService = this.getService(serviceName);
         if (existingService) {
+            // Keep the allocated port stable, but refresh service metadata from latest scan
+            Object.assign(existingService, service);
             return existingService.port;
         }
         const nextPort = this.nextAvailablePort;

package/dist/foundation/Proxy.js

@@ -28,10 +28,12 @@ export class Proxy {
         this.routingTable = await this.buildRoutingTable(branchContexts);
         this.showSummary(port);
         this.startServer(port);
-        this.startWatching();
         console.log(`\n🚀 Proxy server running on http://localhost:${port}`);
         console.log(`📊 Dashboard: http://localhost:${port}`);
         console.log('\nPress Ctrl+C to stop.\n');
+        // Watchers can take noticeable time to initialize on large trees.
+        // Start them after startup logs so the proxy appears ready immediately.
+        setImmediate(() => this.startWatching());
     }
     stop() {
         this.stopWatching?.();
@@ -47,12 +49,13 @@ export class Proxy {
             try {
                 const generated = await loadGeneratedServicesFile(branchContext);
                 for (const service of generated.services) {
-                    const { proxyUrl, url, key, name } = getServiceOutputs(this.context, branchContext, service);
+                    const { proxyUrl, url, key, name, healthCheckUrl } = getServiceOutputs(this.context, branchContext, service);
                     table.set(key, {
                         branchName: branchContext.branchName,
                         serviceName: name,
                         url,
                         proxyUrl,
+                        healthCheckUrl,
                     });
                 }
             }

package/dist/foundation/types/Services.js

@@ -16,6 +16,7 @@ export class ServiceDefinition {
     name;
     type = 'http'; // Phase 1: HTTP only, but extensible
     path; // HTTP only, e.g., "/api"
+    healthCheckPath; // HTTP only, e.g., "/health"
 }
 __decorate([
     IsString(),
@@ -31,6 +32,11 @@ __decorate([
     IsString(),
     __metadata("design:type", String)
 ], ServiceDefinition.prototype, "path", void 0);
+__decorate([
+    IsOptional(),
+    IsString(),
+    __metadata("design:type", String)
+], ServiceDefinition.prototype, "healthCheckPath", void 0);
 /**
  * Services declaration from .forge/services.json
  */

package/dist/lib/proxy-dashboard.js

@@ -1,24 +1,9 @@
-import http from 'http';
-async function checkHealth(target) {
-    return new Promise((resolve) => {
-        const req = http.get(target, { timeout: 2000 }, (res) => {
-            res.resume();
-            resolve(true);
-        });
-        req.on('error', () => resolve(false));
-        req.on('timeout', () => {
-            req.destroy();
-            resolve(false);
-        });
-    });
-}
 export async function handleDashboardRequest(req, res, routingTable, proxyPort) {
     const statuses = [];
-    const checks = Array.from(routingTable.entries()).map(async ([key, route]) => {
-        const healthy = await checkHealth(route.url);
-        statuses.push({ key, route, healthy });
+    Array.from(routingTable.entries()).forEach(([, route], index) => {
+        const rowId = `${route.branchName}::${route.serviceName}::${index}`;
+        statuses.push({ id: encodeURIComponent(rowId), route, status: 'PENDING' });
     });
-    await Promise.all(checks);
     statuses.sort((a, b) => a.route.branchName.localeCompare(b.route.branchName) || a.route.serviceName.localeCompare(b.route.serviceName));
     const grouped = new Map();
     for (const s of statuses) {
@@ -28,27 +13,28 @@ export async function handleDashboardRequest(req, res, routingTable, proxyPort)
     }
     const rows = Array.from(grouped.entries())
         .map(([branchName, services]) => {
-        const header = `<tr class="branch-header"><td colspan="4"><strong>${branchName}</strong></td></tr>`;
+        const header = `<tr class="branch-header"><td colspan="5"><strong>${branchName}</strong></td></tr>`;
         const serviceRows = services
             .map((s) => {
-            const statusBadge = s.healthy
-                ? '<span style="color:#22c55e;font-weight:bold">● UP</span>'
-                : '<span style="color:#ef4444;font-weight:bold">● DOWN</span>';
-            return `<tr>
+            return `<tr data-health-row="${s.id}">
                     <td>${s.route.serviceName}</td>
                     <td><a href="${s.route.proxyUrl}" target="_blank">${s.route.proxyUrl}</a></td>
                     <td><a href="${s.route.url}" target="_blank">${s.route.url}</a></td>
-                    <td>${statusBadge}</td>
+                    <td><a href="${s.route.healthCheckUrl}" target="_blank">${s.route.healthCheckUrl}</a></td>
+                    <td data-health-status="${s.id}"><span style="color:#f59e0b;font-weight:bold">● ${s.status}</span></td>
                 </tr>`;
         })
             .join('\n');
         return header + '\n' + serviceRows;
     })
         .join('\n');
+    const healthTargets = statuses.map((s) => ({
+        id: s.id,
+        url: s.route.healthCheckUrl,
+    }));
     const html = `<!DOCTYPE html>
 <html><head>
 <meta charset="utf-8">
-<meta http-equiv="refresh" content="30">
 <title>Feat-Forge Proxy Dashboard</title>
 <style>
   body { font-family: system-ui, sans-serif; margin: 2rem; background: #0f172a; color: #e2e8f0; }
@@ -66,9 +52,47 @@ export async function handleDashboardRequest(req, res, routingTable, proxyPort)
 <h1>Feat-Forge Proxy Dashboard</h1>
 <p class="meta">${statuses.length} routes &middot; auto-refresh 30s &middot; proxy port ${proxyPort}</p>
 <table>
-<thead><tr><th>Service</th><th>Proxy URL</th><th>Target</th><th>Status</th></tr></thead>
-<tbody>${rows || '<tr><td colspan="4" style="text-align:center;color:#64748b">No routes configured. Run <code>forge services scan</code> on active branches.</td></tr>'}</tbody>
+<thead><tr><th>Service</th><th>Proxy URL</th><th>Target</th><th>Health Check</th><th>Status</th></tr></thead>
+<tbody>${rows || '<tr><td colspan="5" style="text-align:center;color:#64748b">No routes configured. Run <code>forge services scan</code> on active branches.</td></tr>'}</tbody>
 </table>
+<script>
+const healthTargets = ${JSON.stringify(healthTargets)};
+const HEALTH_TIMEOUT_MS = 1200;
+const REFRESH_EVERY_MS = 30000;
+
+function setStatus(id, label, color) {
+  const el = document.querySelector('[data-health-status="' + id + '"]');
+  if (!el) return;
+  el.innerHTML = '<span style="color:' + color + ';font-weight:bold">● ' + label + '</span>';
+}
+
+async function checkHealth(url) {
+  const controller = new AbortController();
+  const timer = setTimeout(() => controller.abort(), HEALTH_TIMEOUT_MS);
+  try {
+    // no-cors allows probing reachability from the browser without requiring CORS headers.
+    await fetch(url, { mode: 'no-cors', cache: 'no-store', signal: controller.signal });
+    return true;
+  } catch {
+    return false;
+  } finally {
+    clearTimeout(timer);
+  }
+}
+
+async function refreshStatuses() {
+  await Promise.all(healthTargets.map(async ({ id, url }) => {
+    setStatus(id, 'PENDING', '#f59e0b');
+    const healthy = await checkHealth(url);
+    setStatus(id, healthy ? 'UP' : 'DOWN', healthy ? '#22c55e' : '#ef4444');
+  }));
+}
+
+if (healthTargets.length > 0) {
+  refreshStatuses();
+  setInterval(refreshStatuses, REFRESH_EVERY_MS);
+}
+</script>
 </body></html>`;
     res.writeHead(200, { 'Content-Type': 'text/html; charset=utf-8' });
     res.end(html);

package/dist/lib/services.js

@@ -119,6 +119,7 @@ export function getServiceOutputs(forgeContext, branchContext, service) {
     const urlSlug = slugify(service.name, false);
     const branchSlug = branchContext.branchNameSlug;
     const proxyPort = forgeContext.options.proxy.port;
+    const healthCheckPath = service.healthCheckPath || service.path || '/';
     return {
         ...service,
         branchSlug,
@@ -128,5 +129,6 @@ export function getServiceOutputs(forgeContext, branchContext, service) {
         urlSlug: urlSlug,
         url: `${service.type}://localhost:${service.port}${service.path || ''}`,
         proxyUrl: `${service.type}://${branchSlug}.${urlSlug}.localhost:${proxyPort}${service.path || ''}`,
+        healthCheckUrl: `${service.type}://localhost:${service.port}${healthCheckPath}`,
     };
 }

package/dist/templates/agent/CONTEXT.code.md

@@ -4,8 +4,8 @@ This project is **process-first**: changes must be deliberate, reviewable, and v
 
 ## Golden Rules (must follow)
 
-1. **Read the feature spec files first (in this order), they are in the .active-feature folder:**
-    - `../FEATURE.md`
+1. **Read the feature spec files first (in this order), they are in the .active-spec folder:**
+    - `../SPEC.md`
     - `../TODO.md`
 
 2. **Do not implement code blindly.**
@@ -26,7 +26,7 @@ This project is **process-first**: changes must be deliberate, reviewable, and v
 
 5. **Always keep the spec in sync.**
     - If you implement something, update `TODO.md` (checklist / status).
-    - If you make a design choice, record it in a sub section in `FEATURE.md`.
+    - If you make a design choice, record it in a sub section in `SPEC.md`.
 
 6. **No secrets / no destructive actions.**
     - Don’t touch credentials, `.env`, keys, or user-specific configs.
@@ -39,7 +39,7 @@ Protect your context window, use subagent to protecte it
 1. **Read specifications**
 
 - Use a subagent **TODO Reader** to read the specifications files and extract actionable tasks, clarifying and prioritizing them as needed :
-    - `../FEATURE.md`
+    - `../SPEC.md`
     - `../TODO.md`
 - Use it to define clear independant code tasks
 
@@ -62,11 +62,11 @@ Protect your context window, use subagent to protecte it
 
 Its a TODO Reader agent for the current feature.
 
-His job is to extract, clarify, and prioritize actionable tasks from `TODO.md`, based on concepts in `FEATURE.md`. Specs files are here : - `../FEATURE.md` - `../TODO.md`
+His job is to extract, clarify, and prioritize actionable tasks from `TODO.md`, based on concepts in `SPEC.md`. Specs files are here : - `../SPEC.md` - `../TODO.md`
 
 #### Responsibilities
 
-- Read and understand the feature specification in `FEATURE.md`.
+- Read and understand the feature specification in `SPEC.md`.
 - Read and understand every item in `TODO.md`.
 - Clarify ambiguities by asking questions if needed.
 - Output a clear, actionable list of tasks for implementation by other agents, ensuring each task is specific, measurable, and feasible.
@@ -138,7 +138,7 @@ A step is “done” only if:
 - The changes are implemented
 - `TODO.md` is updated accordingly
 - Verification steps are provided (and ideally runnable)
-- Any new major design choice is recorded in `FEATURE.md`
+- Any new major design choice is recorded in `SPEC.md`
 
 ## If something is missing
 

package/dist/templates/agent/CONTEXT.spec.md

@@ -2,7 +2,7 @@
 
 This project is **process-first**: clarity before code, all changes must go through the feature specification files:
 
-- `../FEATURE.md`
+- `../SPEC.md`
 - `../TODO.md`
 
 You are currently in **SPEC MODE** / **PLAN MODE**.
@@ -14,13 +14,13 @@ You must only modify the specification files and not touch application code.
 
 ## Golden Rules
 
-1. **Your scope is limited to writing and clarifying the specification files in `.active-feature`:**
-    - `../FEATURE.md`
+1. **Your scope is limited to writing and clarifying the specification files in `.active-spec`:**
+    - `../SPEC.md`
     - `../TODO.md`
       You can update them as much as needed.
 
 2. **Do not modify application code.**
-    - Only files in `.active-feature` should be modified
+    - Only files in `.active-spec` should be modified
     - No modification of source files, tests, or build scripts elsewhere in the project
     - If code changes are needed, express them as tasks or points to clarify in the specs.
 
@@ -28,15 +28,15 @@ You must only modify the specification files and not touch application code.
     - If something is unclear, ask the user in the chat.
     - Prefer questions, options, and trade-offs over premature conclusions.
     - Ask questions one by one or in small batches (max 4 at a time).
-    - Use the answers to enrich and clarify `FEATURE.md`.
+    - Use the answers to enrich and clarify `SPEC.md`.
 
 4. **All proposals must be traceable.**
     - Avoid vague suggestions like "we should consider X" without writing it in the specification.
-    - Any idea or question must be asked to the user and the answer added to `FEATURE.md` or `TODO.md`.
+    - Any idea or question must be asked to the user and the answer added to `SPEC.md` or `TODO.md`.
 
 5. **Use user answers to enrich the specification.**
     - The user can edit the files, reread them each time to see if decisions have been made.
-    - Move answers to the appropriate section of `FEATURE.md` or add tasks in `TODO.md`.
+    - Move answers to the appropriate section of `SPEC.md` or add tasks in `TODO.md`.
 
 6. **No irreversible or destructive actions.**
     - Do not touch credentials, `.env`, keys, or user configs.
@@ -72,7 +72,7 @@ You are not optimizing for speed, but for **shared understanding**.
     - risks and assumptions
     - alternative designs
     - good architecture practices
-- Improve the structure and wording of `FEATURE.md` and `TODO.md`
+- Improve the structure and wording of `SPEC.md` and `TODO.md`
 - Actively modify these two files
 
 ---
@@ -82,7 +82,7 @@ You are not optimizing for speed, but for **shared understanding**.
 - **Think in layers**: intent → constraints → decisions → tasks
 - Prefer explicit over implicit
 - Prefer writing things down over remembering them
-- All important decisions must be made explicit in `FEATURE.md` or as tasks in `TODO.md`
+- All important decisions must be made explicit in `SPEC.md` or as tasks in `TODO.md`
 - No part of the implementation relies on “we’ll figure it out later”
 - If you cannot confidently improve the spec: ask questions
 

package/dist/templates/agent/Copilot/Specs.agent.md

@@ -23,7 +23,7 @@ handoffs:
 
 You are a SPECIFICATION AGENT, NOT an implementation agent.
 
-You are pairing with the user to create a clear, detailed, and actionable specification for the given feature and any user feedback. Your iterative <workflow> loops through gathering context, asking questions and updating the specification files (`FEATURE.md` and `TODO.md`), then back to gathering more context based on user feedback.
+You are pairing with the user to create a clear, detailed, and actionable specification for the given feature and any user feedback. Your iterative <workflow> loops through gathering context, asking questions and updating the specification files (`SPEC.md` and `TODO.md`), then back to gathering more context based on user feedback.
 
 The path to the specification files are :
 %%--COPILOT_SPEC_FILES--%%
@@ -31,7 +31,7 @@ The path to the specification files are :
 Your SOLE responsibility is to clarify, structure, and complete the feature specification. NEVER start implementation or modify application code.
 
 <stopping_rules>
-STOP IMMEDIATELY if you consider starting implementation, switching to implementation mode, or editing any file outside of `FEATURE.md` and `TODO.md` in `.active-feature`.
+STOP IMMEDIATELY if you consider starting implementation, switching to implementation mode, or editing any file outside of `SPEC.md` and `TODO.md` in `.active-spec`.
 
 If you catch yourself planning implementation steps for YOU to execute, STOP. Your job is to update the specification files for the USER or another agent to implement later.
 </stopping_rules>
@@ -49,7 +49,7 @@ If #tool:agent/runSubagent tool is NOT available, run <spec_research> via tools
 
 ## 2. Update the specification files:
 
-1. Update `FEATURE.md` and `TODO.md` directly with all clarifications, responses, and structure improvements.
+1. Update `SPEC.md` and `TODO.md` directly with all clarifications, responses, and structure improvements.
 2. Pause for user feedback, framing this as a draft for review.
 
 ## 3. Handle user feedback:

package/dist/templates/agent/Copilot/SpecsCommit.agent.md

@@ -13,7 +13,7 @@ handoffs:
       showContinueOn: false
 ---
 
-You are a SPECIFICATION COMMIT MESSAGE AGENT. Your role is to prepare a commit message for the specification changes made in the `FEATURE.md` and `TODO.md` files :
+You are a SPECIFICATION COMMIT MESSAGE AGENT. Your role is to prepare a commit message for the specification changes made in the `SPEC.md` and `TODO.md` files :
 %%--COPILOT_SPEC_FILES--%%
 
 Your commit message should follow the repository conventions and clearly indicate that the commit contains specification updates.

package/dist/templates/agent/Copilot/TODO-Reader.agent.md

@@ -6,12 +6,12 @@ tools: ['search', 'read', 'todo']
 
 You are a TODO Reader agent for the current feature.
 
-Your job is to extract, clarify, and prioritize actionable tasks from `TODO.md`, based on concepts in `FEATURE.md`. Specs files are here :
+Your job is to extract, clarify, and prioritize actionable tasks from `TODO.md`, based on concepts in `SPEC.md`. Specs files are here :
 %%--COPILOT_SPEC_FILES--%%
 
 ## Responsibilities
 
-- Read and understand the feature specification in `FEATURE.md`.
+- Read and understand the feature specification in `SPEC.md`.
 - Read and understand every item in `TODO.md`.
 - Clarify ambiguities by asking questions if needed.
 - Output a clear, actionable list of tasks for implementation by other agents, ensuring each task is specific, measurable, and feasible.

package/package.json

@@ -1,9 +1,10 @@
 {
   "name": "feat-forge",
-  "version": "1.1.0",
+  "version": "1.2.3",
   "description": "Feature-first CLI workflow tool for building software at scale with AI agents. Organize specs, parallelize work across repos and agents, and switch contexts without losing track.",
   "license": "AGPL-3.0-only",
   "type": "module",
+  "packageManager": "pnpm@10.29.3",
   "author": {
     "name": "Emmanuel Gauthier",
     "email": "dev@anorake.net"
@@ -40,6 +41,21 @@
   "files": [
     "dist"
   ],
+  "scripts": {
+    "build": "pnpm run build:clean && pnpm run build:transpile && pnpm run build:copy && pnpm run build:permissions",
+    "build:clean": "rm -rf dist",
+    "build:transpile": "tsc -p tsconfig.build.json && tsc-alias -p tsconfig.build.json",
+    "build:copy": "cp -r src/templates dist/",
+    "build:permissions": "chmod +x dist/cli.js",
+    "format": "prettier --write .",
+    "format:check": "prettier --check .",
+    "lint": "tsc --noEmit -p tsconfig.json",
+    "lint:fix": "pnpm lint",
+    "test": "vitest run",
+    "test:watch": "vitest watch",
+    "test:coverage": "vitest run --coverage",
+    "generate:errors": "tsx scripts/generate-errors.ts"
+  },
   "dependencies": {
     "@inquirer/prompts": "^8.2.0",
     "class-transformer": "^0.5.1",
@@ -59,18 +75,5 @@
     "typescript": "^5.9.3",
     "vite-tsconfig-paths": "^6.1.0",
     "vitest": "^4.0.18"
-  },
-  "scripts": {
-    "build": "pnpm run build:clean && pnpm run build:transpile && pnpm run build:copy && pnpm run build:permissions",
-    "build:clean": "rm -rf dist",
-    "build:transpile": "tsc -p tsconfig.build.json && tsc-alias -p tsconfig.build.json",
-    "build:copy": "cp -r src/templates dist/",
-    "build:permissions": "chmod +x dist/cli.js",
-    "format": "prettier --write .",
-    "format:check": "prettier --check .",
-    "test": "vitest run",
-    "test:watch": "vitest watch",
-    "test:coverage": "vitest run --coverage",
-    "generate:errors": "tsx scripts/generate-errors.ts"
   }
-}
+}