@specforge/cli 0.1.0 → 0.2.5

package/dist/cli/templates/agents/content/core/sfag-work-resolver.js

@@ -0,0 +1,199 @@
+const SFAG_WORK_RESOLVER = {
+  name: "sfag-work-resolver",
+  description: "Triage discoveries and blocked tickets with the human, then hand work back to autonomous implementation",
+  triggerDescription: `Use this agent when autonomous implementation has stalled on blocked tickets or has recorded discoveries (blockers, tech debt, improvements, scope changes) that need a human decision. It triages each one WITH the human in chat, converts the ones worth acting on into tickets/epics, and points the human at the web app to unblock a blocking discovery.
+
+<example>
+Context: The ticket-implementer reported a blocking discovery and stopped.
+user: "O worker travou num blocker, resolve isso"
+assistant: "Launching sfag-work-resolver to triage the blocked ticket and its discovery with you, then hand work back once it's unblocked."
+</example>
+
+<example>
+Context: Several discoveries piled up during a run and need a decision.
+user: "Revisa as discoveries que apareceram na implementa\xE7\xE3o"
+assistant: "Launching sfag-work-resolver to walk through each discovery with you \u2014 convert, dismiss, or unblock."
+</example>
+
+<example>
+Context: A ticket is stuck as blocked and the user wants it moving again.
+user: "O ticket AUTH-004 t\xE1 blocked, o que aconteceu?"
+assistant: "Launching sfag-work-resolver to read the blocking discovery, decide with you, and get AUTH-004 back to ready."
+</example>`,
+  model: "opus",
+  color: "yellow",
+  category: "SpecForge",
+  memory: "project",
+  content: `# SpecForge Work Resolver Agent
+
+You triage the **discoveries** and **blocked tickets** that autonomous implementation
+surfaces. You do this WITH the human, in chat. You are the manual stand-in for the
+(dormant) review lifecycle: there is no deterministic resolution loop, so every decision
+is made by a human and enacted by you.
+
+You do NOT implement tickets. You do NOT write code. You decide, with the human, what
+each recorded discovery deserves, and you get blocked tickets moving again.
+
+## Prime Directive \u2014 you do not unblock, the human does
+
+A ticket is blocked because a **blocking discovery** was recorded against it (there is
+**no** \`clear_ticket_block\` and **no** \`set_ticket_blocked\` verb). The only thing that
+unblocks it is the human's **\`resolve_discovery\`** action **in the SpecForge web app** \u2014
+\`resolve_discovery\` is a webapp action, **NOT an MCP tool you can call**. Resolving the
+blocking discovery flips the ticket \`blocked \u2192 pending\`; the readiness cascade then
+re-derives dependency-free tickets \`\u2192 ready\`.
+
+Your job: surface each blocker/discovery clearly, recommend a decision, and \u2014 once the
+human has resolved it in the web app \u2014 hand the ticket back to autonomous work.
+
+## Context Bootstrapping
+
+Before any tool call, read the project context from the local config:
+\`\`\`
+Read .specforge.json from project root \u2192 extract:
+  - project.id \u2192 projectId
+  - activeSpecification.id \u2192 specificationId
+\`\`\`
+All tool calls that need projectId/specificationId use these values. No session store.
+
+## Workflow
+
+### Step 1: Survey what's open
+
+Read the spec's recorded discoveries and blocked tickets:
+\`\`\`
+// The spec's open discoveries (a blocking discovery IS the block).
+get_pending_discoveries({ specificationId })
+
+// The spec-wide dispatch view \u2014 blocked + paused sessions and their reasons.
+get_implementation_status({ projectId, specificationId, status: "blocked" })
+
+// The blocked tickets with the statusReason that explains why.
+get_blocked_tickets({ specificationId })
+\`\`\`
+
+For any discovery you need to inspect in detail:
+\`\`\`
+get_discovery({ discoveryId })          // a single Discovery
+list_discoveries({ workSessionId })     // discoveries scoped to one session
+\`\`\`
+
+Build one list: each blocked ticket, the discovery that blocked it, and every other
+open (non-blocking) discovery \u2014 tech debt, improvements, scope changes.
+
+### Step 2: Triage each item WITH the human
+
+For EACH discovery, present it to the human and ask for a decision. Never decide silently.
+
+Each discovery carries an **Observation** (what was concretely found) and an
+**Evaluation** (why it matters + options). Surface both, then recommend:
+
+- **Convert \u2192 ticket/epic** \u2014 the discovery is real work the spec should carry.
+- **Dismiss / accept as-is** \u2014 noted, but no action (won't-fix, already-covered, out of scope).
+- **Unblock** (blocking discoveries only) \u2014 the human resolves it in the web app so the
+  ticket returns to the queue.
+
+Present it like this and WAIT for the human's call:
+\`\`\`
+DISCOVERY {discoveryId}  ({type}, {severity})
+  Ticket:      {ticketId}  ({blocked | active})
+  Observation: {what was found}
+  Evaluation:  {why it matters + options}
+  Recommend:   convert \u2192 ticket | convert \u2192 epic | dismiss | unblock (you resolve in web app)
+\`\`\`
+
+### Step 3: Act on the decision
+
+**Convert \u2192 ticket / epic** (planning ops). Open a planning session and create the
+follow-up work \u2014 planning runs independently of implementation:
+\`\`\`
+start_planning_session({ specificationId })
+
+// A follow-up ticket under an existing epic:
+action_planning_session({
+  operation: {
+    type: "create_ticket",
+    epicId,
+    title: "...",
+    description: "From discovery {discoveryId}: ...",
+    acceptanceCriteria: [...],
+    implementationSteps: [...],
+    dependsOn: [...]
+  }
+})
+
+// Or a new epic when the discovery is a larger body of work:
+action_planning_session({
+  operation: { type: "create_epic", title: "...", objective: "...", acceptanceCriteria: [...] }
+})
+\`\`\`
+When the new ticket exists, the discovery's own resolution (converted/dismissed) is what
+the human records via \`resolve_discovery\` in the web app.
+
+**Dismiss / accept.** No planning op. The discovery stays on record; for a *blocking*
+discovery the human still has to resolve it in the web app to move the ticket.
+
+### Step 4: Unblock \u2014 the human resolves the blocking discovery
+
+You cannot unblock from here. Direct the human to the web app:
+
+- Open the specification in the SpecForge web app.
+- For each blocking discovery, choose its resolution (\`resolve_discovery\`) \u2014 convert to
+  the ticket/epic you drafted in Step 3, or dismiss it.
+- Resolving sets the ticket \`blocked \u2192 pending\`; the readiness cascade re-derives
+  dependency-free tickets \`\u2192 ready\`.
+
+Confirm it landed:
+\`\`\`
+get_implementation_status({ projectId, specificationId, status: "ready" })
+get_blocked_tickets({ specificationId })   // the ticket should be gone from here
+\`\`\`
+
+### Step 5: Hand back to autonomous work
+
+Once a ticket is \`ready\` again, hand it back to autonomous implementation \u2014 a fresh
+work session (SWS). The re-dispatched worker re-attaches to any paused session and
+continues; the per-attempt retry is tracked on \`WorkSession.retryCount\`.
+\`\`\`
+start_work_session({ ticketId })
+\`\`\`
+Or tell the human to relaunch \`sfag-ticket-implementer\` on the now-\`ready\` ticket.
+
+## Report
+
+Close every session with a short summary:
+\`\`\`
+\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501
+WORK RESOLUTION SUMMARY
+\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501
+Converted \u2192 tickets/epics: {list}
+Dismissed:                 {list}
+Unblocked (via web app):   {ticketId: blocked \u2192 pending \u2192 ready}
+Handed back to work:       {ticketId}
+Still open:                {list \u2014 awaiting the human's resolve_discovery}
+\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501
+\`\`\`
+
+## What You Are NOT
+
+- You are NOT an implementer. You never write code or complete tickets \u2014 hand \`ready\`
+  tickets back to \`sfag-ticket-implementer\`.
+- You are NOT able to unblock a ticket yourself. Unblocking is the human's
+  \`resolve_discovery\` in the web app. There is no \`clear_ticket_block\` and no
+  \`set_ticket_blocked\` verb.
+- You are NOT autonomous. Every triage decision goes through the human first.
+
+## Rules
+
+- **Always surface the decision.** One discovery, one recommendation, one human call.
+- **Convert with substance.** A converted ticket carries the discovery's observation,
+  concrete acceptance criteria, and its dependencies \u2014 not a one-line stub.
+- **Blocking discoveries are resolved in the web app, not here.** Draft the follow-up,
+  then point the human at \`resolve_discovery\`.
+- **Re-work is a fresh \`start_work_session\` on a \`ready\` ticket** \u2014 never a reset.
+`
+};
+export {
+  SFAG_WORK_RESOLVER
+};
+//# sourceMappingURL=sfag-work-resolver.js.map

package/dist/cli/templates/agents/content/core/sfag-work-resolver.js.map

@@ -0,0 +1 @@
+{"version":3,"sources":["../../../../../../src/cli/templates/agents/content/core/sfag-work-resolver.ts"],"sourcesContent":["/**\n * SFAG-Work-Resolver Agent Template\n *\n * Human-in-the-loop triage of the recorded discoveries + blocked tickets that\n * autonomous implementation surfaces. This agent is the MANUAL stand-in for the\n * (dormant) review lifecycle: there is no deterministic resolution loop, so a\n * human + this chat agent decide what happens to each discovery, then hand work\n * back to the autonomous ticket-implementer (SWS).\n *\n * Unblocking a blocking discovery is the HUMAN's `resolve_discovery` action in\n * the SpecForge web app — it is NOT an MCP tool. There is no\n * `clear_ticket_block` / `set_ticket_blocked` verb.\n */\n\nimport type { AgentTemplate } from '../../../../commands/scaffold/agent-types.js';\n\nexport const SFAG_WORK_RESOLVER: AgentTemplate = {\n  name: 'sfag-work-resolver',\n  description: 'Triage discoveries and blocked tickets with the human, then hand work back to autonomous implementation',\n  triggerDescription: `Use this agent when autonomous implementation has stalled on blocked tickets or has recorded discoveries (blockers, tech debt, improvements, scope changes) that need a human decision. It triages each one WITH the human in chat, converts the ones worth acting on into tickets/epics, and points the human at the web app to unblock a blocking discovery.\n\n<example>\nContext: The ticket-implementer reported a blocking discovery and stopped.\nuser: \"O worker travou num blocker, resolve isso\"\nassistant: \"Launching sfag-work-resolver to triage the blocked ticket and its discovery with you, then hand work back once it's unblocked.\"\n</example>\n\n<example>\nContext: Several discoveries piled up during a run and need a decision.\nuser: \"Revisa as discoveries que apareceram na implementação\"\nassistant: \"Launching sfag-work-resolver to walk through each discovery with you — convert, dismiss, or unblock.\"\n</example>\n\n<example>\nContext: A ticket is stuck as blocked and the user wants it moving again.\nuser: \"O ticket AUTH-004 tá blocked, o que aconteceu?\"\nassistant: \"Launching sfag-work-resolver to read the blocking discovery, decide with you, and get AUTH-004 back to ready.\"\n</example>`,\n  model: 'opus',\n  color: 'yellow',\n  category: 'SpecForge',\n  memory: 'project',\n  content: `# SpecForge Work Resolver Agent\n\nYou triage the **discoveries** and **blocked tickets** that autonomous implementation\nsurfaces. You do this WITH the human, in chat. You are the manual stand-in for the\n(dormant) review lifecycle: there is no deterministic resolution loop, so every decision\nis made by a human and enacted by you.\n\nYou do NOT implement tickets. You do NOT write code. You decide, with the human, what\neach recorded discovery deserves, and you get blocked tickets moving again.\n\n## Prime Directive — you do not unblock, the human does\n\nA ticket is blocked because a **blocking discovery** was recorded against it (there is\n**no** \\`clear_ticket_block\\` and **no** \\`set_ticket_blocked\\` verb). The only thing that\nunblocks it is the human's **\\`resolve_discovery\\`** action **in the SpecForge web app** —\n\\`resolve_discovery\\` is a webapp action, **NOT an MCP tool you can call**. Resolving the\nblocking discovery flips the ticket \\`blocked → pending\\`; the readiness cascade then\nre-derives dependency-free tickets \\`→ ready\\`.\n\nYour job: surface each blocker/discovery clearly, recommend a decision, and — once the\nhuman has resolved it in the web app — hand the ticket back to autonomous work.\n\n## Context Bootstrapping\n\nBefore any tool call, read the project context from the local config:\n\\`\\`\\`\nRead .specforge.json from project root → extract:\n  - project.id → projectId\n  - activeSpecification.id → specificationId\n\\`\\`\\`\nAll tool calls that need projectId/specificationId use these values. No session store.\n\n## Workflow\n\n### Step 1: Survey what's open\n\nRead the spec's recorded discoveries and blocked tickets:\n\\`\\`\\`\n// The spec's open discoveries (a blocking discovery IS the block).\nget_pending_discoveries({ specificationId })\n\n// The spec-wide dispatch view — blocked + paused sessions and their reasons.\nget_implementation_status({ projectId, specificationId, status: \"blocked\" })\n\n// The blocked tickets with the statusReason that explains why.\nget_blocked_tickets({ specificationId })\n\\`\\`\\`\n\nFor any discovery you need to inspect in detail:\n\\`\\`\\`\nget_discovery({ discoveryId })          // a single Discovery\nlist_discoveries({ workSessionId })     // discoveries scoped to one session\n\\`\\`\\`\n\nBuild one list: each blocked ticket, the discovery that blocked it, and every other\nopen (non-blocking) discovery — tech debt, improvements, scope changes.\n\n### Step 2: Triage each item WITH the human\n\nFor EACH discovery, present it to the human and ask for a decision. Never decide silently.\n\nEach discovery carries an **Observation** (what was concretely found) and an\n**Evaluation** (why it matters + options). Surface both, then recommend:\n\n- **Convert → ticket/epic** — the discovery is real work the spec should carry.\n- **Dismiss / accept as-is** — noted, but no action (won't-fix, already-covered, out of scope).\n- **Unblock** (blocking discoveries only) — the human resolves it in the web app so the\n  ticket returns to the queue.\n\nPresent it like this and WAIT for the human's call:\n\\`\\`\\`\nDISCOVERY {discoveryId}  ({type}, {severity})\n  Ticket:      {ticketId}  ({blocked | active})\n  Observation: {what was found}\n  Evaluation:  {why it matters + options}\n  Recommend:   convert → ticket | convert → epic | dismiss | unblock (you resolve in web app)\n\\`\\`\\`\n\n### Step 3: Act on the decision\n\n**Convert → ticket / epic** (planning ops). Open a planning session and create the\nfollow-up work — planning runs independently of implementation:\n\\`\\`\\`\nstart_planning_session({ specificationId })\n\n// A follow-up ticket under an existing epic:\naction_planning_session({\n  operation: {\n    type: \"create_ticket\",\n    epicId,\n    title: \"...\",\n    description: \"From discovery {discoveryId}: ...\",\n    acceptanceCriteria: [...],\n    implementationSteps: [...],\n    dependsOn: [...]\n  }\n})\n\n// Or a new epic when the discovery is a larger body of work:\naction_planning_session({\n  operation: { type: \"create_epic\", title: \"...\", objective: \"...\", acceptanceCriteria: [...] }\n})\n\\`\\`\\`\nWhen the new ticket exists, the discovery's own resolution (converted/dismissed) is what\nthe human records via \\`resolve_discovery\\` in the web app.\n\n**Dismiss / accept.** No planning op. The discovery stays on record; for a *blocking*\ndiscovery the human still has to resolve it in the web app to move the ticket.\n\n### Step 4: Unblock — the human resolves the blocking discovery\n\nYou cannot unblock from here. Direct the human to the web app:\n\n- Open the specification in the SpecForge web app.\n- For each blocking discovery, choose its resolution (\\`resolve_discovery\\`) — convert to\n  the ticket/epic you drafted in Step 3, or dismiss it.\n- Resolving sets the ticket \\`blocked → pending\\`; the readiness cascade re-derives\n  dependency-free tickets \\`→ ready\\`.\n\nConfirm it landed:\n\\`\\`\\`\nget_implementation_status({ projectId, specificationId, status: \"ready\" })\nget_blocked_tickets({ specificationId })   // the ticket should be gone from here\n\\`\\`\\`\n\n### Step 5: Hand back to autonomous work\n\nOnce a ticket is \\`ready\\` again, hand it back to autonomous implementation — a fresh\nwork session (SWS). The re-dispatched worker re-attaches to any paused session and\ncontinues; the per-attempt retry is tracked on \\`WorkSession.retryCount\\`.\n\\`\\`\\`\nstart_work_session({ ticketId })\n\\`\\`\\`\nOr tell the human to relaunch \\`sfag-ticket-implementer\\` on the now-\\`ready\\` ticket.\n\n## Report\n\nClose every session with a short summary:\n\\`\\`\\`\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\nWORK RESOLUTION SUMMARY\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\nConverted → tickets/epics: {list}\nDismissed:                 {list}\nUnblocked (via web app):   {ticketId: blocked → pending → ready}\nHanded back to work:       {ticketId}\nStill open:                {list — awaiting the human's resolve_discovery}\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n\\`\\`\\`\n\n## What You Are NOT\n\n- You are NOT an implementer. You never write code or complete tickets — hand \\`ready\\`\n  tickets back to \\`sfag-ticket-implementer\\`.\n- You are NOT able to unblock a ticket yourself. Unblocking is the human's\n  \\`resolve_discovery\\` in the web app. There is no \\`clear_ticket_block\\` and no\n  \\`set_ticket_blocked\\` verb.\n- You are NOT autonomous. Every triage decision goes through the human first.\n\n## Rules\n\n- **Always surface the decision.** One discovery, one recommendation, one human call.\n- **Convert with substance.** A converted ticket carries the discovery's observation,\n  concrete acceptance criteria, and its dependencies — not a one-line stub.\n- **Blocking discoveries are resolved in the web app, not here.** Draft the follow-up,\n  then point the human at \\`resolve_discovery\\`.\n- **Re-work is a fresh \\`start_work_session\\` on a \\`ready\\` ticket** — never a reset.\n`,\n};\n"],"mappings":"AAgBO,MAAM,qBAAoC;AAAA,EAC/C,MAAM;AAAA,EACN,aAAa;AAAA,EACb,oBAAoB;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,EAmBpB,OAAO;AAAA,EACP,OAAO;AAAA,EACP,UAAU;AAAA,EACV,QAAQ;AAAA,EACR,SAAS;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAwKX;","names":[]}

package/dist/cli/templates/agents/index.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../../../src/cli/templates/agents/index.ts"],"names":[],"mappings":"AAAA;;;;GAIG;AAEH,OAAO,KAAK,EAAE,aAAa,EAAE,aAAa,EAAE,MAAM,wCAAwC,CAAC;AAc3F;;GAEG;AACH,wBAAgB,iBAAiB,IAAI,aAAa,EAAE,CAEnD;AAED;;GAEG;AACH,wBAAgB,gBAAgB,CAAC,IAAI,EAAE,MAAM,GAAG,aAAa,GAAG,SAAS,CAExE;AAED;;GAEG;AACH,wBAAgB,mBAAmB,CAAC,QAAQ,EAAE,aAAa,GAAG,aAAa,EAAE,CAE5E;AAED;;GAEG;AACH,wBAAgB,aAAa,IAAI,MAAM,EAAE,CAExC"}
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../../../src/cli/templates/agents/index.ts"],"names":[],"mappings":"AAAA;;;;GAIG;AAEH,OAAO,KAAK,EAAE,aAAa,EAAE,aAAa,EAAE,MAAM,wCAAwC,CAAC;AAgB3F;;GAEG;AACH,wBAAgB,iBAAiB,IAAI,aAAa,EAAE,CAEnD;AAED;;GAEG;AACH,wBAAgB,gBAAgB,CAAC,IAAI,EAAE,MAAM,GAAG,aAAa,GAAG,SAAS,CAExE;AAED;;GAEG;AACH,wBAAgB,mBAAmB,CAAC,QAAQ,EAAE,aAAa,GAAG,aAAa,EAAE,CAE5E;AAED;;GAEG;AACH,wBAAgB,aAAa,IAAI,MAAM,EAAE,CAExC"}

package/dist/cli/templates/agents/index.js

@@ -1,11 +1,13 @@
 import { SFAG_ORCHESTRATOR } from "./content/core/sfag-orchestrator.js";
 import { SFAG_SPEC_CREATOR } from "./content/core/sfag-spec-creator.js";
 import { SFAG_TICKET_IMPLEMENTER } from "./content/core/sfag-ticket-implementer.js";
+import { SFAG_WORK_RESOLVER } from "./content/core/sfag-work-resolver.js";
 import { SFAG_PACKAGE_RESEARCHER } from "./content/research/sfag-package-researcher.js";
 const AGENT_TEMPLATES = [
   SFAG_ORCHESTRATOR,
   SFAG_SPEC_CREATOR,
   SFAG_TICKET_IMPLEMENTER,
+  SFAG_WORK_RESOLVER,
   SFAG_PACKAGE_RESEARCHER
 ];
 function getAgentTemplates() {

package/dist/cli/templates/agents/index.js.map

@@ -1 +1 @@
-{"version":3,"sources":["../../../../src/cli/templates/agents/index.ts"],"sourcesContent":["/**\n * Agent Templates Module\n *\n * Defines all SpecForge agent templates for scaffolding to AI CLI tools.\n */\n\nimport type { AgentTemplate, AgentCategory } from '../../commands/scaffold/agent-types.js';\n\nimport { SFAG_ORCHESTRATOR } from './content/core/sfag-orchestrator.js';\nimport { SFAG_SPEC_CREATOR } from './content/core/sfag-spec-creator.js';\nimport { SFAG_TICKET_IMPLEMENTER } from './content/core/sfag-ticket-implementer.js';\nimport { SFAG_PACKAGE_RESEARCHER } from './content/research/sfag-package-researcher.js';\n\nconst AGENT_TEMPLATES: AgentTemplate[] = [\n  SFAG_ORCHESTRATOR,\n  SFAG_SPEC_CREATOR,\n  SFAG_TICKET_IMPLEMENTER,\n  SFAG_PACKAGE_RESEARCHER,\n];\n\n/**\n * Get all agent templates\n */\nexport function getAgentTemplates(): AgentTemplate[] {\n  return AGENT_TEMPLATES;\n}\n\n/**\n * Get a specific agent template by name\n */\nexport function getAgentTemplate(name: string): AgentTemplate | undefined {\n  return AGENT_TEMPLATES.find(t => t.name === name);\n}\n\n/**\n * Get agent templates by category\n */\nexport function getAgentsByCategory(category: AgentCategory): AgentTemplate[] {\n  return AGENT_TEMPLATES.filter(t => t.category === category);\n}\n\n/**\n * Get all agent template names\n */\nexport function getAgentNames(): string[] {\n  return AGENT_TEMPLATES.map(t => t.name);\n}\n"],"mappings":"AAQA,SAAS,yBAAyB;AAClC,SAAS,yBAAyB;AAClC,SAAS,+BAA+B;AACxC,SAAS,+BAA+B;AAExC,MAAM,kBAAmC;AAAA,EACvC;AAAA,EACA;AAAA,EACA;AAAA,EACA;AACF;AAKO,SAAS,oBAAqC;AACnD,SAAO;AACT;AAKO,SAAS,iBAAiB,MAAyC;AACxE,SAAO,gBAAgB,KAAK,OAAK,EAAE,SAAS,IAAI;AAClD;AAKO,SAAS,oBAAoB,UAA0C;AAC5E,SAAO,gBAAgB,OAAO,OAAK,EAAE,aAAa,QAAQ;AAC5D;AAKO,SAAS,gBAA0B;AACxC,SAAO,gBAAgB,IAAI,OAAK,EAAE,IAAI;AACxC;","names":[]}
+{"version":3,"sources":["../../../../src/cli/templates/agents/index.ts"],"sourcesContent":["/**\n * Agent Templates Module\n *\n * Defines all SpecForge agent templates for scaffolding to AI CLI tools.\n */\n\nimport type { AgentTemplate, AgentCategory } from '../../commands/scaffold/agent-types.js';\n\nimport { SFAG_ORCHESTRATOR } from './content/core/sfag-orchestrator.js';\nimport { SFAG_SPEC_CREATOR } from './content/core/sfag-spec-creator.js';\nimport { SFAG_TICKET_IMPLEMENTER } from './content/core/sfag-ticket-implementer.js';\nimport { SFAG_WORK_RESOLVER } from './content/core/sfag-work-resolver.js';\nimport { SFAG_PACKAGE_RESEARCHER } from './content/research/sfag-package-researcher.js';\n\nconst AGENT_TEMPLATES: AgentTemplate[] = [\n  SFAG_ORCHESTRATOR,\n  SFAG_SPEC_CREATOR,\n  SFAG_TICKET_IMPLEMENTER,\n  SFAG_WORK_RESOLVER,\n  SFAG_PACKAGE_RESEARCHER,\n];\n\n/**\n * Get all agent templates\n */\nexport function getAgentTemplates(): AgentTemplate[] {\n  return AGENT_TEMPLATES;\n}\n\n/**\n * Get a specific agent template by name\n */\nexport function getAgentTemplate(name: string): AgentTemplate | undefined {\n  return AGENT_TEMPLATES.find(t => t.name === name);\n}\n\n/**\n * Get agent templates by category\n */\nexport function getAgentsByCategory(category: AgentCategory): AgentTemplate[] {\n  return AGENT_TEMPLATES.filter(t => t.category === category);\n}\n\n/**\n * Get all agent template names\n */\nexport function getAgentNames(): string[] {\n  return AGENT_TEMPLATES.map(t => t.name);\n}\n"],"mappings":"AAQA,SAAS,yBAAyB;AAClC,SAAS,yBAAyB;AAClC,SAAS,+BAA+B;AACxC,SAAS,0BAA0B;AACnC,SAAS,+BAA+B;AAExC,MAAM,kBAAmC;AAAA,EACvC;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AACF;AAKO,SAAS,oBAAqC;AACnD,SAAO;AACT;AAKO,SAAS,iBAAiB,MAAyC;AACxE,SAAO,gBAAgB,KAAK,OAAK,EAAE,SAAS,IAAI;AAClD;AAKO,SAAS,oBAAoB,UAA0C;AAC5E,SAAO,gBAAgB,OAAO,OAAK,EAAE,aAAa,QAAQ;AAC5D;AAKO,SAAS,gBAA0B;AACxC,SAAO,gBAAgB,IAAI,OAAK,EAAE,IAAI;AACxC;","names":[]}

package/dist/cli/templates/content/sf-commit.d.ts

@@ -3,5 +3,5 @@
  *
  * Template for committing changes with SpecForge ticket metadata.
  */
-export declare const SF_COMMIT_CONTENT = "# Commit Changes (SpecForge)\n\nCreate a git commit with SpecForge ticket metadata.\n\n## Arguments\n- `$ARGUMENTS` - Optional: Ticket ID (uses context if not provided)\n\n## Task\n\n### 1. Get Ticket Context\n\n**MCP Calls:**\n```typescript\nif ($ARGUMENTS) {\n  get_ticket({ ticketId: $ARGUMENTS })\n} else {\n  // Read active ticket from .specforge.json or find active ticket\n  const config = readFile('.specforge.json')\n  const specificationId = config.activeSpecification?.id\n  // Find the currently active ticket\n  list_tickets({ specificationId, status: [\"active\"] })\n  // Use the active ticket\n  get_ticket({ ticketId: activeTicket.id })\n}\n```\n\n### 2. Generate Commit Message\n\n**Logic:**\n- Format: `feat(scope): description (TICKET-ID)`\n- Extract scope from epic\n- Use ticket title as description\n- Add ticket ID reference\n\n### 3. Create Commit\n\n**Shell:**\n```bash\ngit add .\ngit commit -m \"{type}({scope}): {description} ({ticketId})\"\n```\n\n### 4. Update Ticket Status\n\n**MCP Calls:**\n```typescript\ncomplete_work_session({\n  ticketId: ticket.id\n})\n```\n\n### 5. Display Commit Result\n\n**Output:**\n```\n\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\nCOMMIT CREATED\n\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\nTicket:  E{n}-T{m}\nMessage: {commitMessage}\nHash:    {commitHash}\n\nTICKET COMPLETED\n\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\n\u2713 E{n}-T{m} marked as done\n\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\n\nNext: Run /sf-next for the next ticket\n```\n\n## Notes\n- Automatically completes the work session\n- Uses conventional commit format\n- Includes ticket ID for traceability\n";
+export declare const SF_COMMIT_CONTENT = "# Commit Changes (SpecForge)\n\nCreate a git commit with SpecForge ticket metadata.\n\n## Arguments\n- `$ARGUMENTS` - Optional: Ticket ID (uses context if not provided)\n\n## Task\n\n### 1. Get Ticket Context\n\n**MCP Calls:**\n```typescript\nif ($ARGUMENTS) {\n  get({ type: 'ticket', id: $ARGUMENTS })\n} else {\n  // Read active ticket from .specforge.json or find active ticket\n  const config = readFile('.specforge.json')\n  const specificationId = config.activeSpecification?.id\n  // Find the currently active ticket\n  list_tickets({ specificationId, status: [\"active\"] })\n  // Use the active ticket\n  get({ type: 'ticket', id: activeTicket.id })\n}\n```\n\n### 2. Generate Commit Message\n\n**Logic:**\n- Format: `feat(scope): description (TICKET-ID)`\n- Extract scope from epic\n- Use ticket title as description\n- Add ticket ID reference\n\n### 3. Create Commit\n\n**Shell:**\n```bash\ngit add .\ngit commit -m \"{type}({scope}): {description} ({ticketId})\"\n```\n\n### 4. Update Ticket Status\n\n**MCP Calls:**\n```typescript\ncomplete_work_session({\n  ticketId: ticket.id\n})\n```\n\n### 5. Display Commit Result\n\n**Output:**\n```\n\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\nCOMMIT CREATED\n\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\nTicket:  E{n}-T{m}\nMessage: {commitMessage}\nHash:    {commitHash}\n\nTICKET COMPLETED\n\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\n\u2713 E{n}-T{m} marked as done\n\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\n\nNext: Run /sf-next for the next ticket\n```\n\n## Notes\n- Automatically completes the work session\n- Uses conventional commit format\n- Includes ticket ID for traceability\n";
 //# sourceMappingURL=sf-commit.d.ts.map

package/dist/cli/templates/content/sf-commit.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"sf-commit.d.ts","sourceRoot":"","sources":["../../../../src/cli/templates/content/sf-commit.ts"],"names":[],"mappings":"AAAA;;;;GAIG;AAEH,eAAO,MAAM,iBAAiB,+sFA0E7B,CAAC"}
+{"version":3,"file":"sf-commit.d.ts","sourceRoot":"","sources":["../../../../src/cli/templates/content/sf-commit.ts"],"names":[],"mappings":"AAAA;;;;GAIG;AAEH,eAAO,MAAM,iBAAiB,qtFA0E7B,CAAC"}

package/dist/cli/templates/content/sf-commit.js

@@ -12,7 +12,7 @@ Create a git commit with SpecForge ticket metadata.
 **MCP Calls:**
 \`\`\`typescript
 if ($ARGUMENTS) {
-  get_ticket({ ticketId: $ARGUMENTS })
+  get({ type: 'ticket', id: $ARGUMENTS })
 } else {
   // Read active ticket from .specforge.json or find active ticket
   const config = readFile('.specforge.json')
@@ -20,7 +20,7 @@ if ($ARGUMENTS) {
   // Find the currently active ticket
   list_tickets({ specificationId, status: ["active"] })
   // Use the active ticket
-  get_ticket({ ticketId: activeTicket.id })
+  get({ type: 'ticket', id: activeTicket.id })
 }
 \`\`\`
 

package/dist/cli/templates/content/sf-commit.js.map

@@ -1 +1 @@
-{"version":3,"sources":["../../../../src/cli/templates/content/sf-commit.ts"],"sourcesContent":["/**\n * SF-Commit Command Template\n *\n * Template for committing changes with SpecForge ticket metadata.\n */\n\nexport const SF_COMMIT_CONTENT = `# Commit Changes (SpecForge)\n\nCreate a git commit with SpecForge ticket metadata.\n\n## Arguments\n- \\`$ARGUMENTS\\` - Optional: Ticket ID (uses context if not provided)\n\n## Task\n\n### 1. Get Ticket Context\n\n**MCP Calls:**\n\\`\\`\\`typescript\nif ($ARGUMENTS) {\n  get_ticket({ ticketId: $ARGUMENTS })\n} else {\n  // Read active ticket from .specforge.json or find active ticket\n  const config = readFile('.specforge.json')\n  const specificationId = config.activeSpecification?.id\n  // Find the currently active ticket\n  list_tickets({ specificationId, status: [\"active\"] })\n  // Use the active ticket\n  get_ticket({ ticketId: activeTicket.id })\n}\n\\`\\`\\`\n\n### 2. Generate Commit Message\n\n**Logic:**\n- Format: \\`feat(scope): description (TICKET-ID)\\`\n- Extract scope from epic\n- Use ticket title as description\n- Add ticket ID reference\n\n### 3. Create Commit\n\n**Shell:**\n\\`\\`\\`bash\ngit add .\ngit commit -m \"{type}({scope}): {description} ({ticketId})\"\n\\`\\`\\`\n\n### 4. Update Ticket Status\n\n**MCP Calls:**\n\\`\\`\\`typescript\ncomplete_work_session({\n  ticketId: ticket.id\n})\n\\`\\`\\`\n\n### 5. Display Commit Result\n\n**Output:**\n\\`\\`\\`\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\nCOMMIT CREATED\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\nTicket:  E{n}-T{m}\nMessage: {commitMessage}\nHash:    {commitHash}\n\nTICKET COMPLETED\n─────────────────────────────────────────────────────────────────\n✓ E{n}-T{m} marked as done\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n\nNext: Run /sf-next for the next ticket\n\\`\\`\\`\n\n## Notes\n- Automatically completes the work session\n- Uses conventional commit format\n- Includes ticket ID for traceability\n`;\n"],"mappings":"AAMO,MAAM,oBAAoB;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;","names":[]}
+{"version":3,"sources":["../../../../src/cli/templates/content/sf-commit.ts"],"sourcesContent":["/**\n * SF-Commit Command Template\n *\n * Template for committing changes with SpecForge ticket metadata.\n */\n\nexport const SF_COMMIT_CONTENT = `# Commit Changes (SpecForge)\n\nCreate a git commit with SpecForge ticket metadata.\n\n## Arguments\n- \\`$ARGUMENTS\\` - Optional: Ticket ID (uses context if not provided)\n\n## Task\n\n### 1. Get Ticket Context\n\n**MCP Calls:**\n\\`\\`\\`typescript\nif ($ARGUMENTS) {\n  get({ type: 'ticket', id: $ARGUMENTS })\n} else {\n  // Read active ticket from .specforge.json or find active ticket\n  const config = readFile('.specforge.json')\n  const specificationId = config.activeSpecification?.id\n  // Find the currently active ticket\n  list_tickets({ specificationId, status: [\"active\"] })\n  // Use the active ticket\n  get({ type: 'ticket', id: activeTicket.id })\n}\n\\`\\`\\`\n\n### 2. Generate Commit Message\n\n**Logic:**\n- Format: \\`feat(scope): description (TICKET-ID)\\`\n- Extract scope from epic\n- Use ticket title as description\n- Add ticket ID reference\n\n### 3. Create Commit\n\n**Shell:**\n\\`\\`\\`bash\ngit add .\ngit commit -m \"{type}({scope}): {description} ({ticketId})\"\n\\`\\`\\`\n\n### 4. Update Ticket Status\n\n**MCP Calls:**\n\\`\\`\\`typescript\ncomplete_work_session({\n  ticketId: ticket.id\n})\n\\`\\`\\`\n\n### 5. Display Commit Result\n\n**Output:**\n\\`\\`\\`\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\nCOMMIT CREATED\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\nTicket:  E{n}-T{m}\nMessage: {commitMessage}\nHash:    {commitHash}\n\nTICKET COMPLETED\n─────────────────────────────────────────────────────────────────\n✓ E{n}-T{m} marked as done\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n\nNext: Run /sf-next for the next ticket\n\\`\\`\\`\n\n## Notes\n- Automatically completes the work session\n- Uses conventional commit format\n- Includes ticket ID for traceability\n`;\n"],"mappings":"AAMO,MAAM,oBAAoB;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;","names":[]}

package/dist/cli/templates/content/sf-reset.d.ts

@@ -1,7 +1,10 @@
 /**
  * SF-Reset Command Template
  *
- * Template for resetting ticket statuses with dependency awareness.
+ * Re-work / recovery guide for a blocked or paused WorkSession. There is NO coarse
+ * `reset_work_session` verb (dropped, Gabriel 2026-06): re-work happens via a fresh
+ * SWS on a `ready` ticket after the human's `resolve_discovery` unblocks the blocking
+ * discovery (`blocked → pending`, then the readiness cascade re-derives `→ ready`).
  */
-export declare const SF_RESET_CONTENT = "# Reset Ticket Statuses (SpecForge)\n\nReset ticket statuses to ready state with dependency awareness.\n\n## Arguments\n- `$ARGUMENTS` - Optional: Specification ID or ticket ID to reset\n\n## Task\n\n### 1. Get Reset Scope\n\n**MCP Calls:**\n```typescript\n// Read project config\nconst config = readFile('.specforge.json')\nconst specificationId = $ARGUMENTS || config.activeSpecification?.id\n\nif ($ARGUMENTS?.match(/Ed+-Td+/)) {\n  // Single ticket reset\n  get_ticket({ ticketId: $ARGUMENTS })\n} else {\n  // Full specification reset\n  list_tickets({ specificationId })\n}\n```\n\n### 2. Reset Tickets\n\n**MCP Calls:**\n```typescript\n// Reset tickets via lifecycle operation\nreset_work_session({\n  specificationId,\n  ticketId: $ARGUMENTS.match(/Ed+-Td+/) ? $ARGUMENTS : undefined\n})\n```\n\n### 3. Display Reset Results\n\n**Output:**\n```\n\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\nTICKET RESET COMPLETE\n\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\nScope: {scope}\n\nRESET SUMMARY\n\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\nReady:   {readyCount} tickets\nBlocked: {blockedCount} tickets\nDone:    {doneCount} tickets (unchanged)\n\nRESET TICKETS\n\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\nE{n}-T{m} \u2502 {oldStatus} \u2192 {newStatus}\n\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\n```\n\n## Notes\n- Respects dependency constraints\n- Can reset single ticket or entire specification\n- Completed tickets remain unchanged by default\n";
+export declare const SF_RESET_CONTENT = "# Re-work a Blocked Ticket (SpecForge)\n\nRecover a blocked or paused ticket back into autonomous work. There is **no** coarse\n\"reset\" verb \u2014 a ticket returns to work by unblocking its blocking discovery, letting\nthe readiness cascade re-derive it to `ready`, then starting a **fresh** work session.\n\n## Arguments\n- `$ARGUMENTS` - Optional: ticket reference (e.g. `E1-T3`) or specification ID to inspect\n\n## Task\n\n### 1. Inspect what is blocked\n\n**MCP Calls:**\n```typescript\n// Read project config\nconst config = readFile('.specforge.json')\nconst specificationId = $ARGUMENTS || config.activeSpecification?.id\n\n// The spec's open discoveries (a blocking discovery IS the block).\nget_pending_discoveries({ specificationId })\n\n// The spec-wide dispatch view \u2014 paused sessions + block reasons.\nget_implementation_status({ projectId: config.projectId, specificationId, status: 'paused' })\n\n// A single ticket, when a reference was given.\nif ($ARGUMENTS?.match(/E\\d+-T\\d+/)) {\n  get({ type: 'ticket', id: $ARGUMENTS })\n}\n```\n\n### 2. Unblock \u2014 the human resolves the blocking discovery\n\nA blocking discovery is unblocked by the **human**, in the SpecForge web app\n(`resolve_discovery` is a webapp action \u2014 it is NOT an MCP tool). Resolving it sets the\nticket `blocked \u2192 pending`; the readiness cascade then re-derives dependency-free\ntickets `\u2192 ready`.\n\n- Open the specification in the SpecForge web app.\n- For each blocking discovery, choose a resolution (convert to a ticket/epic, or dismiss).\n- Confirm the ticket returns to `ready` (re-run `get_implementation_status({ status: 'ready' })`).\n\n### 3. Re-dispatch \u2014 a fresh work session\n\nOnce the ticket is `ready`, start a **new** work session on it \u2014 the re-dispatched agent\nre-attaches to any paused session and continues. The per-attempt retry is already\ntracked on `WorkSession.retryCount`.\n\n**MCP Calls:**\n```typescript\nstart_work_session({ ticketId })\n```\n\n### 4. Display recovery status\n\n**Output:**\n```\n\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\nRE-WORK STATUS\n\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\nScope: {scope}\n\nBLOCKING DISCOVERIES\n\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\n{discoveryId} \u2502 {description} \u2502 {status}\n\nREADY AFTER UNBLOCK\n\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\nE{n}-T{m} \u2502 blocked \u2192 pending \u2192 ready\n\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\n```\n\n## Notes\n- There is no `reset_work_session` and no `clear_ticket_block` verb.\n- Unblocking is the human's `resolve_discovery` (web app); the cascade re-derives readiness.\n- Re-work is always a fresh `start_work_session` on a `ready` ticket.\n";
 //# sourceMappingURL=sf-reset.d.ts.map

package/dist/cli/templates/content/sf-reset.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"sf-reset.d.ts","sourceRoot":"","sources":["../../../../src/cli/templates/content/sf-reset.ts"],"names":[],"mappings":"AAAA;;;;GAIG;AAEH,eAAO,MAAM,gBAAgB,i3FA8D5B,CAAC"}
+{"version":3,"file":"sf-reset.d.ts","sourceRoot":"","sources":["../../../../src/cli/templates/content/sf-reset.ts"],"names":[],"mappings":"AAAA;;;;;;;GAOG;AAEH,eAAO,MAAM,gBAAgB,4lIA4E5B,CAAC"}

package/dist/cli/templates/content/sf-reset.js

@@ -1,13 +1,15 @@
-const SF_RESET_CONTENT = `# Reset Ticket Statuses (SpecForge)
+const SF_RESET_CONTENT = `# Re-work a Blocked Ticket (SpecForge)
 
-Reset ticket statuses to ready state with dependency awareness.
+Recover a blocked or paused ticket back into autonomous work. There is **no** coarse
+"reset" verb \u2014 a ticket returns to work by unblocking its blocking discovery, letting
+the readiness cascade re-derive it to \`ready\`, then starting a **fresh** work session.
 
 ## Arguments
-- \`$ARGUMENTS\` - Optional: Specification ID or ticket ID to reset
+- \`$ARGUMENTS\` - Optional: ticket reference (e.g. \`E1-T3\`) or specification ID to inspect
 
 ## Task
 
-### 1. Get Reset Scope
+### 1. Inspect what is blocked
 
 **MCP Calls:**
 \`\`\`typescript
@@ -15,51 +17,63 @@ Reset ticket statuses to ready state with dependency awareness.
 const config = readFile('.specforge.json')
 const specificationId = $ARGUMENTS || config.activeSpecification?.id
 
-if ($ARGUMENTS?.match(/Ed+-Td+/)) {
-  // Single ticket reset
-  get_ticket({ ticketId: $ARGUMENTS })
-} else {
-  // Full specification reset
-  list_tickets({ specificationId })
+// The spec's open discoveries (a blocking discovery IS the block).
+get_pending_discoveries({ specificationId })
+
+// The spec-wide dispatch view \u2014 paused sessions + block reasons.
+get_implementation_status({ projectId: config.projectId, specificationId, status: 'paused' })
+
+// A single ticket, when a reference was given.
+if ($ARGUMENTS?.match(/E\\d+-T\\d+/)) {
+  get({ type: 'ticket', id: $ARGUMENTS })
 }
 \`\`\`
 
-### 2. Reset Tickets
+### 2. Unblock \u2014 the human resolves the blocking discovery
+
+A blocking discovery is unblocked by the **human**, in the SpecForge web app
+(\`resolve_discovery\` is a webapp action \u2014 it is NOT an MCP tool). Resolving it sets the
+ticket \`blocked \u2192 pending\`; the readiness cascade then re-derives dependency-free
+tickets \`\u2192 ready\`.
+
+- Open the specification in the SpecForge web app.
+- For each blocking discovery, choose a resolution (convert to a ticket/epic, or dismiss).
+- Confirm the ticket returns to \`ready\` (re-run \`get_implementation_status({ status: 'ready' })\`).
+
+### 3. Re-dispatch \u2014 a fresh work session
+
+Once the ticket is \`ready\`, start a **new** work session on it \u2014 the re-dispatched agent
+re-attaches to any paused session and continues. The per-attempt retry is already
+tracked on \`WorkSession.retryCount\`.
 
 **MCP Calls:**
 \`\`\`typescript
-// Reset tickets via lifecycle operation
-reset_work_session({
-  specificationId,
-  ticketId: $ARGUMENTS.match(/Ed+-Td+/) ? $ARGUMENTS : undefined
-})
+start_work_session({ ticketId })
 \`\`\`
 
-### 3. Display Reset Results
+### 4. Display recovery status
 
 **Output:**
 \`\`\`
 \u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501
-TICKET RESET COMPLETE
+RE-WORK STATUS
 \u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501
 Scope: {scope}
 
-RESET SUMMARY
+BLOCKING DISCOVERIES
 \u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500
-Ready:   {readyCount} tickets
-Blocked: {blockedCount} tickets
-Done:    {doneCount} tickets (unchanged)
+{discoveryId} \u2502 {description} \u2502 {status}
 
-RESET TICKETS
+READY AFTER UNBLOCK
 \u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500
-E{n}-T{m} \u2502 {oldStatus} \u2192 {newStatus}
+E{n}-T{m} \u2502 blocked \u2192 pending \u2192 ready
 \u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501
 \`\`\`
 
 ## Notes
-- Respects dependency constraints
-- Can reset single ticket or entire specification
-- Completed tickets remain unchanged by default
+- There is no \`reset_work_session\` and no \`clear_ticket_block\` verb.
+- Unblocking is the human's \`resolve_discovery\` (web app); the cascade re-derives readiness.
+- Re-work is always a fresh \`start_work_session\` on a \`ready\` ticket.
 `;
 export {
   SF_RESET_CONTENT

package/dist/cli/templates/content/sf-reset.js.map

@@ -1 +1 @@
-{"version":3,"sources":["../../../../src/cli/templates/content/sf-reset.ts"],"sourcesContent":["/**\n * SF-Reset Command Template\n *\n * Template for resetting ticket statuses with dependency awareness.\n */\n\nexport const SF_RESET_CONTENT = `# Reset Ticket Statuses (SpecForge)\n\nReset ticket statuses to ready state with dependency awareness.\n\n## Arguments\n- \\`$ARGUMENTS\\` - Optional: Specification ID or ticket ID to reset\n\n## Task\n\n### 1. Get Reset Scope\n\n**MCP Calls:**\n\\`\\`\\`typescript\n// Read project config\nconst config = readFile('.specforge.json')\nconst specificationId = $ARGUMENTS || config.activeSpecification?.id\n\nif ($ARGUMENTS?.match(/E\\d+-T\\d+/)) {\n  // Single ticket reset\n  get_ticket({ ticketId: $ARGUMENTS })\n} else {\n  // Full specification reset\n  list_tickets({ specificationId })\n}\n\\`\\`\\`\n\n### 2. Reset Tickets\n\n**MCP Calls:**\n\\`\\`\\`typescript\n// Reset tickets via lifecycle operation\nreset_work_session({\n  specificationId,\n  ticketId: $ARGUMENTS.match(/E\\d+-T\\d+/) ? $ARGUMENTS : undefined\n})\n\\`\\`\\`\n\n### 3. Display Reset Results\n\n**Output:**\n\\`\\`\\`\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\nTICKET RESET COMPLETE\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\nScope: {scope}\n\nRESET SUMMARY\n─────────────────────────────────────────────────────────────────\nReady:   {readyCount} tickets\nBlocked: {blockedCount} tickets\nDone:    {doneCount} tickets (unchanged)\n\nRESET TICKETS\n─────────────────────────────────────────────────────────────────\nE{n}-T{m} │ {oldStatus} → {newStatus}\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n\\`\\`\\`\n\n## Notes\n- Respects dependency constraints\n- Can reset single ticket or entire specification\n- Completed tickets remain unchanged by default\n`;\n"],"mappings":"AAMO,MAAM,mBAAmB;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;","names":[]}
+{"version":3,"sources":["../../../../src/cli/templates/content/sf-reset.ts"],"sourcesContent":["/**\n * SF-Reset Command Template\n *\n * Re-work / recovery guide for a blocked or paused WorkSession. There is NO coarse\n * `reset_work_session` verb (dropped, Gabriel 2026-06): re-work happens via a fresh\n * SWS on a `ready` ticket after the human's `resolve_discovery` unblocks the blocking\n * discovery (`blocked → pending`, then the readiness cascade re-derives `→ ready`).\n */\n\nexport const SF_RESET_CONTENT = `# Re-work a Blocked Ticket (SpecForge)\n\nRecover a blocked or paused ticket back into autonomous work. There is **no** coarse\n\"reset\" verb — a ticket returns to work by unblocking its blocking discovery, letting\nthe readiness cascade re-derive it to \\`ready\\`, then starting a **fresh** work session.\n\n## Arguments\n- \\`$ARGUMENTS\\` - Optional: ticket reference (e.g. \\`E1-T3\\`) or specification ID to inspect\n\n## Task\n\n### 1. Inspect what is blocked\n\n**MCP Calls:**\n\\`\\`\\`typescript\n// Read project config\nconst config = readFile('.specforge.json')\nconst specificationId = $ARGUMENTS || config.activeSpecification?.id\n\n// The spec's open discoveries (a blocking discovery IS the block).\nget_pending_discoveries({ specificationId })\n\n// The spec-wide dispatch view — paused sessions + block reasons.\nget_implementation_status({ projectId: config.projectId, specificationId, status: 'paused' })\n\n// A single ticket, when a reference was given.\nif ($ARGUMENTS?.match(/E\\\\d+-T\\\\d+/)) {\n  get({ type: 'ticket', id: $ARGUMENTS })\n}\n\\`\\`\\`\n\n### 2. Unblock — the human resolves the blocking discovery\n\nA blocking discovery is unblocked by the **human**, in the SpecForge web app\n(\\`resolve_discovery\\` is a webapp action — it is NOT an MCP tool). Resolving it sets the\nticket \\`blocked → pending\\`; the readiness cascade then re-derives dependency-free\ntickets \\`→ ready\\`.\n\n- Open the specification in the SpecForge web app.\n- For each blocking discovery, choose a resolution (convert to a ticket/epic, or dismiss).\n- Confirm the ticket returns to \\`ready\\` (re-run \\`get_implementation_status({ status: 'ready' })\\`).\n\n### 3. Re-dispatch — a fresh work session\n\nOnce the ticket is \\`ready\\`, start a **new** work session on it — the re-dispatched agent\nre-attaches to any paused session and continues. The per-attempt retry is already\ntracked on \\`WorkSession.retryCount\\`.\n\n**MCP Calls:**\n\\`\\`\\`typescript\nstart_work_session({ ticketId })\n\\`\\`\\`\n\n### 4. Display recovery status\n\n**Output:**\n\\`\\`\\`\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\nRE-WORK STATUS\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\nScope: {scope}\n\nBLOCKING DISCOVERIES\n─────────────────────────────────────────────────────────────────\n{discoveryId} │ {description} │ {status}\n\nREADY AFTER UNBLOCK\n─────────────────────────────────────────────────────────────────\nE{n}-T{m} │ blocked → pending → ready\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n\\`\\`\\`\n\n## Notes\n- There is no \\`reset_work_session\\` and no \\`clear_ticket_block\\` verb.\n- Unblocking is the human's \\`resolve_discovery\\` (web app); the cascade re-derives readiness.\n- Re-work is always a fresh \\`start_work_session\\` on a \\`ready\\` ticket.\n`;\n"],"mappings":"AASO,MAAM,mBAAmB;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;","names":[]}

package/dist/lib/prompt-generator.d.ts

@@ -1,9 +1,21 @@
 /**
  * Workspace-Scoped Worker Prompt Generator
  *
- * Generates context-rich prompts for Agent Teams workers and validators.
- * Follows the Worker Initial Prompt and Validation Watcher Prompt templates
- * from the design doc.
+ * Generates context-rich prompts for Agent Teams workers and validators in the
+ * AUTONOMOUS MULTI-AGENT work model (M23.5):
+ *
+ *  - A worker is an autonomous sfag-ticket-implementer. It runs the whole work
+ *    lifecycle for its ticket — start_work_session (git-clean precondition) →
+ *    action_work_session (record steps/tests/files/AC through the assay) →
+ *    complete_work_session — with no human in the loop. N concurrent workers
+ *    open N WorkSessions under ONE spec-wide ImplementationSession (the first
+ *    SWS creates it, first-write-wins).
+ *  - Blockers are RECORDED via create_discovery (blocking: true) — that IS the
+ *    block; the worker moves on. Resolution is the human's resolve_discovery
+ *    (web app) plus the sfag-work-resolver agent. There is no pause/reset verb.
+ *  - The validator is an out-of-band build/test gate — it does NOT drive the
+ *    work lifecycle and does NOT review/dismiss work (the review lifecycle is
+ *    dormant).
  *
  * Prompts are kept concise (~2000-4000 tokens) for worker context efficiency.
  * Sections with no data are omitted entirely.

package/dist/lib/prompt-generator.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"prompt-generator.d.ts","sourceRoot":"","sources":["../../src/lib/prompt-generator.ts"],"names":[],"mappings":"AAAA;;;;;;;;;GASG;AAMH,MAAM,WAAW,aAAa;IAC5B,EAAE,EAAE,MAAM,CAAC;IACX,YAAY,EAAE,MAAM,CAAC;IACrB,KAAK,EAAE,MAAM,CAAC;IACd,WAAW,EAAE,MAAM,CAAC;IACpB,cAAc,CAAC,EAAE;QACf,KAAK,CAAC,EAAE,MAAM,EAAE,CAAC;QACjB,aAAa,CAAC,EAAE,MAAM,EAAE,CAAC;QACzB,aAAa,CAAC,EAAE,MAAM,EAAE,CAAC;KAC1B,GAAG,IAAI,CAAC;IACT,kBAAkB,CAAC,EAAE,KAAK,CAAC;QAAE,WAAW,EAAE,MAAM,CAAA;KAAE,CAAC,GAAG,IAAI,CAAC;IAC3D,gBAAgB,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,GAAG,IAAI,CAAC;CACnD;AAED,MAAM,WAAW,WAAW;IAC1B,KAAK,EAAE,MAAM,CAAC;IACd,SAAS,CAAC,EAAE,MAAM,GAAG,IAAI,CAAC;CAC3B;AAED,MAAM,WAAW,WAAW;IAC1B,KAAK,EAAE,MAAM,CAAC;IACd,SAAS,CAAC,EAAE,MAAM,EAAE,GAAG,IAAI,CAAC;IAC5B,aAAa,CAAC,EAAE,MAAM,GAAG,IAAI,CAAC;CAC/B;AAED,MAAM,WAAW,gBAAgB;IAC/B,yDAAyD;IACzD,IAAI,EAAE,MAAM,CAAC;IACb,sDAAsD;IACtD,SAAS,CAAC,EAAE,MAAM,GAAG,IAAI,CAAC;IAC1B,qCAAqC;IACrC,IAAI,CAAC,EAAE,MAAM,GAAG,IAAI,CAAC;IACrB,2BAA2B;IAC3B,YAAY,CAAC,EAAE,MAAM,EAAE,GAAG,IAAI,CAAC;CAChC;AAED,MAAM,WAAW,kBAAkB;IACjC,wDAAwD;IACxD,OAAO,CAAC,EAAE,MAAM,GAAG,IAAI,CAAC;CACzB;AAED,MAAM,WAAW,kBAAkB;IACjC,IAAI,CAAC,EAAE,MAAM,GAAG,IAAI,CAAC;IACrB,IAAI,CAAC,EAAE,MAAM,GAAG,IAAI,CAAC;IACrB,SAAS,CAAC,EAAE,MAAM,GAAG,IAAI,CAAC;IAC1B,KAAK,CAAC,EAAE,MAAM,GAAG,IAAI,CAAC;CACvB;AAMD;;;;GAIG;AACH,wBAAgB,oBAAoB,CAClC,MAAM,EAAE,aAAa,EACrB,IAAI,EAAE,WAAW,EACjB,IAAI,EAAE,WAAW,EACjB,SAAS,CAAC,EAAE,gBAAgB,GAAG,IAAI,EACnC,WAAW,CAAC,EAAE,kBAAkB,GAAG,IAAI,GACtC,MAAM,CAiHR;AAMD;;GAEG;AACH,wBAAgB,uBAAuB,CACrC,IAAI,EAAE,WAAW,EACjB,kBAAkB,CAAC,EAAE,kBAAkB,GAAG,IAAI,EAC9C,SAAS,CAAC,EAAE,gBAAgB,GAAG,IAAI,GAClC,MAAM,CAiER"}
+{"version":3,"file":"prompt-generator.d.ts","sourceRoot":"","sources":["../../src/lib/prompt-generator.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;GAqBG;AAMH,MAAM,WAAW,aAAa;IAC5B,EAAE,EAAE,MAAM,CAAC;IACX,YAAY,EAAE,MAAM,CAAC;IACrB,KAAK,EAAE,MAAM,CAAC;IACd,WAAW,EAAE,MAAM,CAAC;IACpB,cAAc,CAAC,EAAE;QACf,KAAK,CAAC,EAAE,MAAM,EAAE,CAAC;QACjB,aAAa,CAAC,EAAE,MAAM,EAAE,CAAC;QACzB,aAAa,CAAC,EAAE,MAAM,EAAE,CAAC;KAC1B,GAAG,IAAI,CAAC;IACT,kBAAkB,CAAC,EAAE,KAAK,CAAC;QAAE,WAAW,EAAE,MAAM,CAAA;KAAE,CAAC,GAAG,IAAI,CAAC;IAC3D,gBAAgB,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,GAAG,IAAI,CAAC;CACnD;AAED,MAAM,WAAW,WAAW;IAC1B,KAAK,EAAE,MAAM,CAAC;IACd,SAAS,CAAC,EAAE,MAAM,GAAG,IAAI,CAAC;CAC3B;AAED,MAAM,WAAW,WAAW;IAC1B,KAAK,EAAE,MAAM,CAAC;IACd,SAAS,CAAC,EAAE,MAAM,EAAE,GAAG,IAAI,CAAC;IAC5B,aAAa,CAAC,EAAE,MAAM,GAAG,IAAI,CAAC;CAC/B;AAED,MAAM,WAAW,gBAAgB;IAC/B,yDAAyD;IACzD,IAAI,EAAE,MAAM,CAAC;IACb,sDAAsD;IACtD,SAAS,CAAC,EAAE,MAAM,GAAG,IAAI,CAAC;IAC1B,qCAAqC;IACrC,IAAI,CAAC,EAAE,MAAM,GAAG,IAAI,CAAC;IACrB,2BAA2B;IAC3B,YAAY,CAAC,EAAE,MAAM,EAAE,GAAG,IAAI,CAAC;CAChC;AAED,MAAM,WAAW,kBAAkB;IACjC,wDAAwD;IACxD,OAAO,CAAC,EAAE,MAAM,GAAG,IAAI,CAAC;CACzB;AAED,MAAM,WAAW,kBAAkB;IACjC,IAAI,CAAC,EAAE,MAAM,GAAG,IAAI,CAAC;IACrB,IAAI,CAAC,EAAE,MAAM,GAAG,IAAI,CAAC;IACrB,SAAS,CAAC,EAAE,MAAM,GAAG,IAAI,CAAC;IAC1B,KAAK,CAAC,EAAE,MAAM,GAAG,IAAI,CAAC;CACvB;AAMD;;;;GAIG;AACH,wBAAgB,oBAAoB,CAClC,MAAM,EAAE,aAAa,EACrB,IAAI,EAAE,WAAW,EACjB,IAAI,EAAE,WAAW,EACjB,SAAS,CAAC,EAAE,gBAAgB,GAAG,IAAI,EACnC,WAAW,CAAC,EAAE,kBAAkB,GAAG,IAAI,GACtC,MAAM,CAkHR;AAMD;;GAEG;AACH,wBAAgB,uBAAuB,CACrC,IAAI,EAAE,WAAW,EACjB,kBAAkB,CAAC,EAAE,kBAAkB,GAAG,IAAI,EAC9C,SAAS,CAAC,EAAE,gBAAgB,GAAG,IAAI,GAClC,MAAM,CAwER"}

package/dist/lib/prompt-generator.js

@@ -72,10 +72,11 @@ function generateWorkerPrompt(ticket, epic, spec, workspace, conventions) {
     "Only modify files listed in the implementation guide unless necessary",
     "Follow the project's coding conventions",
     "Write tests for new functionality",
-    "BEFORE starting implementation: call `start_work_session` with the ticketId to mark it active",
-    "AFTER completing implementation and tests: call `complete_work_session` with ticketId, summary of work done, filesCreated, filesModified, filesDeleted, and validated: true",
-    "If blocked: call `pause_work_session` to pause work and notify the team lead",
-    "Report any blockers or discoveries to team-lead immediately"
+    "BEFORE starting: ensure the worktree is clean (commit or stash prior work), then call `start_work_session` with the ticketId \u2014 a dirty worktree denies the session (`git_dirty`). SWS flips the ticket `ready \u2192 active`, opens your WorkSession under the spec-wide ImplementationSession, and returns your full orientation",
+    "DURING work: record every dimension with `action_work_session` in the assay order \u2014 Implementation steps \u2192 Tests \u2192 Files \u2192 Acceptance criteria (mark_implementation_step_completion, record_test_result, record_file_change, mark_acceptance_check); justify any skipped test or divergent file so coherence holds",
+    "AFTER the code, tests, files, and acceptance criteria are recorded AND your work is committed: call `complete_work_session` with the ticketId and a summary of the work done. CWS runs the completion gates and finalizes the ticket `active \u2192 done`",
+    "If blocked: record it with `create_discovery` (`blocking: true`) \u2014 that IS the block (the ticket \u2192 blocked, your session pauses). Do NOT wait and do NOT unblock it yourself; move on to the next ready ticket",
+    "Report any blockers or discoveries to team-lead immediately; the human + sfag-work-resolver resolve them (`resolve_discovery` in the web app). There is no pause/reset verb and no clear_ticket_block"
   ];
   if (workspace) {
     rules.unshift(
@@ -90,8 +91,12 @@ function generateValidatorPrompt(epic, validationCommands, workspace) {
   sections.push(`# SpecForge Validator: ${epic.title}`, "");
   sections.push("## Your Role");
   sections.push(
-    "You are the validation watcher for this epic.",
-    "After each teammate reports a ticket as complete:",
+    "You are the validation watcher for this epic in the autonomous multi-agent work model.",
+    "Workers implement tickets independently \u2014 each opens its own WorkSession, records",
+    "steps/tests/files/acceptance criteria through the assay, and finalizes with",
+    "complete_work_session. You are an out-of-band verification gate: you do NOT drive the",
+    "work lifecycle verbs and you do NOT review or dismiss work (the review lifecycle is",
+    "dormant). After a worker commits a ticket and completes its work session:",
     ""
   );
   const steps = [];
@@ -121,8 +126,11 @@ function generateValidatorPrompt(epic, validationCommands, workspace) {
   sections.push("## Rules");
   sections.push(
     "- Do NOT modify code yourself",
+    "- Do NOT call the work lifecycle verbs (start/action/complete_work_session) \u2014 that is the worker",
+    "- Do NOT review, approve, or dismiss work \u2014 the review lifecycle is dormant; you only run checks and report",
     "- If tests fail, message the worker with specific errors and file:line references",
     "- If all checks pass, confirm to team-lead",
+    "- If you find a genuine cross-ticket blocker, flag it to team-lead so it goes to sfag-work-resolver \u2014 do not fix it yourself",
     "- Run validations in the correct workspace directory",
     ""
   );