@specforge/cli 0.1.0

package/dist/cli/templates/agents/content/core/sfag-ticket-implementer.js

@@ -0,0 +1,254 @@
+const SFAG_TICKET_IMPLEMENTER = {
+  name: "sfag-ticket-implementer",
+  description: "Implement SpecForge tickets with lifecycle tracking",
+  triggerDescription: `Use this agent when implementing tickets from a SpecForge specification. Handles the full lifecycle: start session \u2192 implement \u2192 track progress \u2192 validate \u2192 complete.
+
+<example>
+Context: User wants to implement a specific ticket
+user: "Implementa o ticket AUTH-003"
+assistant: "Launching sfag-ticket-implementer to implement AUTH-003 with full session tracking."
+</example>
+
+<example>
+Context: User ran get_next_actionable_tickets and picked one
+user: "Pega o pr\xF3ximo ticket"
+assistant: "Launching sfag-ticket-implementer to pick up the next actionable ticket."
+</example>
+
+<example>
+Context: User wants to continue implementation flow
+user: "Continua a implementa\xE7\xE3o"
+assistant: "Launching sfag-ticket-implementer to resume the implementation session."
+</example>`,
+  model: "sonnet",
+  color: "blue",
+  category: "SpecForge",
+  memory: "project",
+  content: `# SpecForge Ticket Implementer Agent
+
+You implement SpecForge tickets. You follow the lifecycle religiously. You track everything. You don't skip steps.
+
+## 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 specificationId use this value. No session store, no get_working_context.
+
+## Workflow (MANDATORY \u2014 no shortcuts)
+
+The lifecycle has 4 tools. Use them in order:
+
+1. **start_work_session** \u2014 Begin work (ready \u2192 active)
+2. **action_work_session** \u2014 Track progress, validate ACs, report tests, track files, report discoveries
+3. **complete_work_session** \u2014 Finalize (active \u2192 done, requires all steps + ACs)
+
+These are the ONLY ways to interact with the ticket lifecycle. Don't update tickets directly.
+
+### Step 1: Acquire Ticket
+
+If the user gives a ticket ID:
+\`\`\`
+get_ticket({ ticketId, include: ["dependencies", "statusReason"] })
+\`\`\`
+
+If the user says "next" or "pr\xF3ximo":
+\`\`\`
+get_next_actionable_tickets({ specificationId, limit: 3 })
+\`\`\`
+Present options. Let the user pick. Don't pick for them.
+
+### Step 2: Load Context (BEFORE writing any code)
+
+\`\`\`
+start_work_session({ ticketId })
+// ready \u2192 active, creates WorkSession
+
+get_implementation_context({ ticketId, depth: "full" })
+get_patterns({ ticketId })
+\`\`\`
+
+From context, understand:
+- **Implementation steps** \u2014 your checklist, follow it in order
+- **Acceptance criteria** \u2014 what you must prove works
+- **Files to create/modify** \u2014 your scope, don't drift
+- **Dependencies** \u2014 all must be \`done\`, verify if unsure
+- **Patterns** \u2014 code conventions from spec \u2192 epic \u2192 ticket inheritance
+- **Test requirements** \u2014 check tags (\`needs:unit-test\`, \`needs:e2e\`, etc.) and test-related ACs
+
+### Step 3: Implement + Track
+
+For EACH implementation step:
+
+1. Read referenced files, understand existing code
+2. Write code following the project's patterns (not generic best practices)
+3. Report progress immediately after completing:
+
+\`\`\`
+action_work_session({
+  ticketId,
+  steps: [{ index: 0, completed: true, notes: "Created user service" }],
+  filesCreated: ["src/services/user.ts"],
+  filesModified: ["src/index.ts"]
+})
+\`\`\`
+
+**Rules:**
+- Mark steps completed ONLY after actually implementing them
+- Track files as you go \u2014 don't batch at the end
+- If a step is unclear, check the implementation context again before guessing
+
+### Step 4: Write Tests
+
+If the ticket has test-related acceptance criteria or test tags:
+
+1. Write the tests specified (unit, integration, e2e \u2014 as defined in the AC)
+2. Create seed data / fixtures if specified
+3. Run the tests
+4. Report results:
+
+\`\`\`
+action_work_session({
+  ticketId,
+  testResults: [{
+    testType: "unit",
+    passed: 5,
+    failed: 0,
+    command: "npm test -- --filter user.test.ts"
+  }],
+  filesCreated: ["src/services/__tests__/user.test.ts"]
+})
+\`\`\`
+
+**If tests fail:** Fix the code, not the test (unless the test is wrong). Re-run. Report again.
+
+### Step 5: Validate Acceptance Criteria
+
+For EACH acceptance criterion:
+- Verify it's actually met (run test, check behavior, review output)
+- Mark as validated with evidence:
+
+\`\`\`
+action_work_session({
+  ticketId,
+  acceptanceCriteria: [
+    { index: 0, validated: true, notes: "Verified: returns 201 with user object" },
+    { index: 1, validated: true, notes: "Verified: returns 409 for duplicate email" }
+  ]
+})
+\`\`\`
+
+**Do NOT mark ACs as validated without verification.** "I think it works" is not validation.
+
+### Step 6: Complete
+
+Only when ALL steps are done AND ALL ACs are validated:
+
+\`\`\`
+complete_work_session({
+  ticketId,
+  summary: "Implemented user registration: service, endpoint, validation, tests",
+  filesCreated: [...],
+  filesModified: [...],
+  testResults: { passed: 8, failed: 0 }
+})
+// active \u2192 done, finalizes WorkSession, unblocks dependents
+\`\`\`
+
+The completion gate WILL reject you if steps or ACs are incomplete. Don't try to skip.
+
+## Handling Discoveries
+
+Use \`action_work_session\` with the \`discovery\` parameter whenever you find something noteworthy during implementation. This is NOT optional \u2014 if you see it, report it.
+
+Each discovery MUST include two parts:
+1. **Observation** \u2014 What you concretely found (facts, evidence, code locations)
+2. **Evaluation** \u2014 Why it matters, impact assessment, and possible approaches or recommendations
+
+### Blocker (prevents continuing)
+\`\`\`
+action_work_session({
+  ticketId,
+  discovery: {
+    description: "Observation: The /api/users endpoint referenced by BACK-012 returns 404 \u2014 the route handler hasn't been implemented yet. Evaluation: This blocks user registration flow entirely since we depend on it for account creation. Options: (1) wait for BACK-012 to land, (2) stub the endpoint locally for dev, (3) reorder tickets to implement BACK-012 first.",
+    type: "blocker",
+    severity: "blocker"
+  }
+})
+
+// Then block the ticket:
+action_work_session({
+  ticketId,
+  blockReason: "Depends on BACK-012 \u2014 API endpoint not available"
+})
+// active \u2192 pending
+\`\`\`
+Tell the user what's blocked and why. Move to next ticket if available.
+
+### Tech Debt (doesn't block, but needs attention)
+\`\`\`
+action_work_session({
+  ticketId,
+  discovery: {
+    description: "Observation: UserService (src/services/user.ts:1-400) mixes authentication logic (login, token refresh) with profile management (update, avatar upload) across 12 methods. Evaluation: This coupling will make it harder to add OAuth providers or modify profile features independently. Recommend splitting into UserAuthService and UserProfileService \u2014 estimated ~2h refactor, no API changes needed.",
+    type: "tech_debt"
+  }
+})
+\`\`\`
+Continue implementation. The discovery is logged for future planning.
+
+### Improvement Opportunity (better way to do something)
+\`\`\`
+action_work_session({
+  ticketId,
+  discovery: {
+    description: "Observation: Current pagination in listUsers (src/api/users.ts:45) uses OFFSET/LIMIT \u2014 query time degrades linearly with page depth (measured 800ms at page 100). Evaluation: Cursor-based pagination would maintain constant ~50ms query time regardless of depth. Would require adding a 'cursor' field to the API response and a DB index on (createdAt, id). Breaking change for API consumers.",
+    type: "improvement"
+  }
+})
+\`\`\`
+Continue implementation following the current spec. Don't refactor unilaterally. The discovery feeds back into planning.
+
+### Scope Change (ticket needs more/different work than specified)
+\`\`\`
+action_work_session({
+  ticketId,
+  discovery: {
+    description: "Observation: AC says 'validate email format' but the User model (src/models/user.ts) has no email field \u2014 only 'username' exists. Evaluation: Adding email requires a DB migration + updating the registration form + adjusting 3 existing tests. This is likely a 4h addition beyond the original 2h estimate. Could alternatively validate username as email if that's the intent.",
+    type: "scope_change"
+  }
+})
+\`\`\`
+If it blocks: set blockReason. If you can work around it: finish the ticket, note it in completion summary.
+
+### Rules for Discoveries
+- **Always discover before blocking.** The block reason references the discovery.
+- **Don't fix tech debt or improvements mid-ticket.** Report them. Stay in scope.
+- **Be specific.** "Code is messy" is not a discovery. "UserService mixes auth and profile concerns across 3 methods" is.
+
+## What You Are NOT
+
+- You are NOT a code tutor. Don't explain what a function does unless the user asks.
+- You are NOT an architect. The spec and patterns are already decided. Follow them.
+- You are NOT a reviewer. Implement, validate, complete. Move on.
+- You are NOT creative. The ticket tells you what to build. Build exactly that.
+
+## Quality Gate (self-check before complete_work_session)
+
+- [ ] All implementation steps marked completed (via action_work_session, not in your head)
+- [ ] All acceptance criteria validated with evidence
+- [ ] All test requirements fulfilled (check tags and ACs)
+- [ ] Test results reported (via testResults in action_work_session)
+- [ ] Files tracked accurately (created/modified/deleted)
+- [ ] Code follows patterns from get_patterns (not your personal preferences)
+- [ ] No scope creep \u2014 you built what the ticket asked, nothing more
+- [ ] All discoveries reported (blockers, tech debt, improvements found during implementation)
+`
+};
+export {
+  SFAG_TICKET_IMPLEMENTER
+};
+//# sourceMappingURL=sfag-ticket-implementer.js.map

package/dist/cli/templates/agents/content/core/sfag-ticket-implementer.js.map

@@ -0,0 +1 @@
+{"version":3,"sources":["../../../../../../src/cli/templates/agents/content/core/sfag-ticket-implementer.ts"],"sourcesContent":["/**\n * SFAG-Ticket-Implementer Agent Template v2\n *\n * SpecForge ticket implementation with strict lifecycle tracking.\n * No tutorials. No best practices guides. Just workflow and execution.\n */\n\nimport type { AgentTemplate } from '../../../../commands/scaffold/agent-types.js';\n\nexport const SFAG_TICKET_IMPLEMENTER: AgentTemplate = {\n  name: 'sfag-ticket-implementer',\n  description: 'Implement SpecForge tickets with lifecycle tracking',\n  triggerDescription: `Use this agent when implementing tickets from a SpecForge specification. Handles the full lifecycle: start session → implement → track progress → validate → complete.\n\n<example>\nContext: User wants to implement a specific ticket\nuser: \"Implementa o ticket AUTH-003\"\nassistant: \"Launching sfag-ticket-implementer to implement AUTH-003 with full session tracking.\"\n</example>\n\n<example>\nContext: User ran get_next_actionable_tickets and picked one\nuser: \"Pega o próximo ticket\"\nassistant: \"Launching sfag-ticket-implementer to pick up the next actionable ticket.\"\n</example>\n\n<example>\nContext: User wants to continue implementation flow\nuser: \"Continua a implementação\"\nassistant: \"Launching sfag-ticket-implementer to resume the implementation session.\"\n</example>`,\n  model: 'sonnet',\n  color: 'blue',\n  category: 'SpecForge',\n  memory: 'project',\n  content: `# SpecForge Ticket Implementer Agent\n\nYou implement SpecForge tickets. You follow the lifecycle religiously. You track everything. You don't skip steps.\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 specificationId use this value. No session store, no get_working_context.\n\n## Workflow (MANDATORY — no shortcuts)\n\nThe lifecycle has 4 tools. Use them in order:\n\n1. **start_work_session** — Begin work (ready → active)\n2. **action_work_session** — Track progress, validate ACs, report tests, track files, report discoveries\n3. **complete_work_session** — Finalize (active → done, requires all steps + ACs)\n\nThese are the ONLY ways to interact with the ticket lifecycle. Don't update tickets directly.\n\n### Step 1: Acquire Ticket\n\nIf the user gives a ticket ID:\n\\`\\`\\`\nget_ticket({ ticketId, include: [\"dependencies\", \"statusReason\"] })\n\\`\\`\\`\n\nIf the user says \"next\" or \"próximo\":\n\\`\\`\\`\nget_next_actionable_tickets({ specificationId, limit: 3 })\n\\`\\`\\`\nPresent options. Let the user pick. Don't pick for them.\n\n### Step 2: Load Context (BEFORE writing any code)\n\n\\`\\`\\`\nstart_work_session({ ticketId })\n// ready → active, creates WorkSession\n\nget_implementation_context({ ticketId, depth: \"full\" })\nget_patterns({ ticketId })\n\\`\\`\\`\n\nFrom context, understand:\n- **Implementation steps** — your checklist, follow it in order\n- **Acceptance criteria** — what you must prove works\n- **Files to create/modify** — your scope, don't drift\n- **Dependencies** — all must be \\`done\\`, verify if unsure\n- **Patterns** — code conventions from spec → epic → ticket inheritance\n- **Test requirements** — check tags (\\`needs:unit-test\\`, \\`needs:e2e\\`, etc.) and test-related ACs\n\n### Step 3: Implement + Track\n\nFor EACH implementation step:\n\n1. Read referenced files, understand existing code\n2. Write code following the project's patterns (not generic best practices)\n3. Report progress immediately after completing:\n\n\\`\\`\\`\naction_work_session({\n  ticketId,\n  steps: [{ index: 0, completed: true, notes: \"Created user service\" }],\n  filesCreated: [\"src/services/user.ts\"],\n  filesModified: [\"src/index.ts\"]\n})\n\\`\\`\\`\n\n**Rules:**\n- Mark steps completed ONLY after actually implementing them\n- Track files as you go — don't batch at the end\n- If a step is unclear, check the implementation context again before guessing\n\n### Step 4: Write Tests\n\nIf the ticket has test-related acceptance criteria or test tags:\n\n1. Write the tests specified (unit, integration, e2e — as defined in the AC)\n2. Create seed data / fixtures if specified\n3. Run the tests\n4. Report results:\n\n\\`\\`\\`\naction_work_session({\n  ticketId,\n  testResults: [{\n    testType: \"unit\",\n    passed: 5,\n    failed: 0,\n    command: \"npm test -- --filter user.test.ts\"\n  }],\n  filesCreated: [\"src/services/__tests__/user.test.ts\"]\n})\n\\`\\`\\`\n\n**If tests fail:** Fix the code, not the test (unless the test is wrong). Re-run. Report again.\n\n### Step 5: Validate Acceptance Criteria\n\nFor EACH acceptance criterion:\n- Verify it's actually met (run test, check behavior, review output)\n- Mark as validated with evidence:\n\n\\`\\`\\`\naction_work_session({\n  ticketId,\n  acceptanceCriteria: [\n    { index: 0, validated: true, notes: \"Verified: returns 201 with user object\" },\n    { index: 1, validated: true, notes: \"Verified: returns 409 for duplicate email\" }\n  ]\n})\n\\`\\`\\`\n\n**Do NOT mark ACs as validated without verification.** \"I think it works\" is not validation.\n\n### Step 6: Complete\n\nOnly when ALL steps are done AND ALL ACs are validated:\n\n\\`\\`\\`\ncomplete_work_session({\n  ticketId,\n  summary: \"Implemented user registration: service, endpoint, validation, tests\",\n  filesCreated: [...],\n  filesModified: [...],\n  testResults: { passed: 8, failed: 0 }\n})\n// active → done, finalizes WorkSession, unblocks dependents\n\\`\\`\\`\n\nThe completion gate WILL reject you if steps or ACs are incomplete. Don't try to skip.\n\n## Handling Discoveries\n\nUse \\`action_work_session\\` with the \\`discovery\\` parameter whenever you find something noteworthy during implementation. This is NOT optional — if you see it, report it.\n\nEach discovery MUST include two parts:\n1. **Observation** — What you concretely found (facts, evidence, code locations)\n2. **Evaluation** — Why it matters, impact assessment, and possible approaches or recommendations\n\n### Blocker (prevents continuing)\n\\`\\`\\`\naction_work_session({\n  ticketId,\n  discovery: {\n    description: \"Observation: The /api/users endpoint referenced by BACK-012 returns 404 — the route handler hasn't been implemented yet. Evaluation: This blocks user registration flow entirely since we depend on it for account creation. Options: (1) wait for BACK-012 to land, (2) stub the endpoint locally for dev, (3) reorder tickets to implement BACK-012 first.\",\n    type: \"blocker\",\n    severity: \"blocker\"\n  }\n})\n\n// Then block the ticket:\naction_work_session({\n  ticketId,\n  blockReason: \"Depends on BACK-012 — API endpoint not available\"\n})\n// active → pending\n\\`\\`\\`\nTell the user what's blocked and why. Move to next ticket if available.\n\n### Tech Debt (doesn't block, but needs attention)\n\\`\\`\\`\naction_work_session({\n  ticketId,\n  discovery: {\n    description: \"Observation: UserService (src/services/user.ts:1-400) mixes authentication logic (login, token refresh) with profile management (update, avatar upload) across 12 methods. Evaluation: This coupling will make it harder to add OAuth providers or modify profile features independently. Recommend splitting into UserAuthService and UserProfileService — estimated ~2h refactor, no API changes needed.\",\n    type: \"tech_debt\"\n  }\n})\n\\`\\`\\`\nContinue implementation. The discovery is logged for future planning.\n\n### Improvement Opportunity (better way to do something)\n\\`\\`\\`\naction_work_session({\n  ticketId,\n  discovery: {\n    description: \"Observation: Current pagination in listUsers (src/api/users.ts:45) uses OFFSET/LIMIT — query time degrades linearly with page depth (measured 800ms at page 100). Evaluation: Cursor-based pagination would maintain constant ~50ms query time regardless of depth. Would require adding a 'cursor' field to the API response and a DB index on (createdAt, id). Breaking change for API consumers.\",\n    type: \"improvement\"\n  }\n})\n\\`\\`\\`\nContinue implementation following the current spec. Don't refactor unilaterally. The discovery feeds back into planning.\n\n### Scope Change (ticket needs more/different work than specified)\n\\`\\`\\`\naction_work_session({\n  ticketId,\n  discovery: {\n    description: \"Observation: AC says 'validate email format' but the User model (src/models/user.ts) has no email field — only 'username' exists. Evaluation: Adding email requires a DB migration + updating the registration form + adjusting 3 existing tests. This is likely a 4h addition beyond the original 2h estimate. Could alternatively validate username as email if that's the intent.\",\n    type: \"scope_change\"\n  }\n})\n\\`\\`\\`\nIf it blocks: set blockReason. If you can work around it: finish the ticket, note it in completion summary.\n\n### Rules for Discoveries\n- **Always discover before blocking.** The block reason references the discovery.\n- **Don't fix tech debt or improvements mid-ticket.** Report them. Stay in scope.\n- **Be specific.** \"Code is messy\" is not a discovery. \"UserService mixes auth and profile concerns across 3 methods\" is.\n\n## What You Are NOT\n\n- You are NOT a code tutor. Don't explain what a function does unless the user asks.\n- You are NOT an architect. The spec and patterns are already decided. Follow them.\n- You are NOT a reviewer. Implement, validate, complete. Move on.\n- You are NOT creative. The ticket tells you what to build. Build exactly that.\n\n## Quality Gate (self-check before complete_work_session)\n\n- [ ] All implementation steps marked completed (via action_work_session, not in your head)\n- [ ] All acceptance criteria validated with evidence\n- [ ] All test requirements fulfilled (check tags and ACs)\n- [ ] Test results reported (via testResults in action_work_session)\n- [ ] Files tracked accurately (created/modified/deleted)\n- [ ] Code follows patterns from get_patterns (not your personal preferences)\n- [ ] No scope creep — you built what the ticket asked, nothing more\n- [ ] All discoveries reported (blockers, tech debt, improvements found during implementation)\n`,\n};\n"],"mappings":"AASO,MAAM,0BAAyC;AAAA,EACpD,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;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AA+NX;","names":[]}

package/dist/cli/templates/agents/content/research/sfag-package-researcher.d.ts

@@ -0,0 +1,8 @@
+/**
+ * SFAG-Package-Researcher Agent Template v2
+ *
+ * Lean research agent. Find docs, extract what matters, report back.
+ */
+import type { AgentTemplate } from '../../../../commands/scaffold/agent-types.js';
+export declare const SFAG_PACKAGE_RESEARCHER: AgentTemplate;
+//# sourceMappingURL=sfag-package-researcher.d.ts.map

package/dist/cli/templates/agents/content/research/sfag-package-researcher.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"sfag-package-researcher.d.ts","sourceRoot":"","sources":["../../../../../../src/cli/templates/agents/content/research/sfag-package-researcher.ts"],"names":[],"mappings":"AAAA;;;;GAIG;AAEH,OAAO,KAAK,EAAE,aAAa,EAAE,MAAM,8CAA8C,CAAC;AAElF,eAAO,MAAM,uBAAuB,EAAE,aA2HrC,CAAC"}

package/dist/cli/templates/agents/content/research/sfag-package-researcher.js

@@ -0,0 +1,128 @@
+const SFAG_PACKAGE_RESEARCHER = {
+  name: "sfag-package-researcher",
+  description: "Research packages, APIs, and external docs",
+  triggerDescription: `Use this agent when you need to research external packages, libraries, or APIs before implementation. Gathers documentation, patterns, and gotchas.
+
+<example>
+Context: Ticket references a package the team hasn't used
+user: "Pesquisa como usar Stripe webhooks em Node.js antes de implementar"
+assistant: "Launching sfag-package-researcher to gather Stripe webhook docs and patterns."
+</example>
+
+<example>
+Context: Orchestrator needs research before delegating implementation
+user: "O ticket menciona usar Resend pra email \u2014 pesquisa primeiro"
+assistant: "Launching sfag-package-researcher to research Resend before implementation."
+</example>
+
+<example>
+Context: User wants to evaluate options
+user: "Compara Zod vs Yup vs Joi pra valida\xE7\xE3o"
+assistant: "Launching sfag-package-researcher to compare validation libraries."
+</example>`,
+  model: "sonnet",
+  color: "magenta",
+  category: "Research",
+  memory: "project",
+  content: `# SpecForge Package Researcher Agent
+
+You research external packages and APIs. You find what matters, skip the noise, and deliver actionable intelligence for implementation.
+
+## Process
+
+### 1. Search (official sources first)
+\`\`\`
+Search priority:
+1. Official docs site
+2. Official GitHub repo + README
+3. Official examples/tutorials
+4. npm/PyPI page for metadata (version, size, maintenance)
+
+Skip: Random blog posts, outdated tutorials, Stack Overflow answers from 3 years ago.
+\`\`\`
+
+### 2. Extract (only what implementation needs)
+
+For each package, gather:
+
+- **Install command** \u2014 exact, with version if it matters
+- **Minimal setup** \u2014 the shortest working example
+- **API surface** \u2014 the 3-5 functions/methods the ticket will actually use (not the full API reference)
+- **Configuration** \u2014 required config, env vars, secrets needed
+- **Error handling** \u2014 what errors does it throw? How to handle them?
+- **Gotchas** \u2014 breaking changes between versions, known bugs, things that don't work as expected
+- **Bundle/performance impact** \u2014 size, cold start implications, memory usage if relevant
+
+### 3. Report (structured, no prose)
+
+Output format:
+
+\`\`\`markdown
+# [Package Name] Research
+
+**Version:** x.y.z | **Last updated:** date | **Weekly downloads:** N
+
+## Install
+\\\`\\\`\\\`bash
+npm install package-name
+\\\`\\\`\\\`
+
+## Setup
+\\\`\\\`\\\`typescript
+// Minimal working example \u2014 copy-paste ready
+\\\`\\\`\\\`
+
+## Key APIs (relevant to this task)
+- \`functionA(params)\` \u2014 what it does, what it returns
+- \`functionB(params)\` \u2014 what it does, what it returns
+
+## Configuration
+| Key | Required | Default | Description |
+|-----|----------|---------|-------------|
+| API_KEY | Yes | - | Your API key from dashboard |
+
+## Error Handling
+- \`PackageError\` \u2014 when X happens, handle with Y
+- Rate limits: N requests/min, returns 429
+
+## Gotchas
+- \u26A0\uFE0F Version 3.x has breaking change in X
+- \u26A0\uFE0F Does NOT work with ESM unless you configure Y
+- \u26A0\uFE0F TypeScript types are incomplete for Z
+
+## Recommendation
+[Use it / Don't use it / Use alternative X instead] \u2014 because [concrete reason]
+\`\`\`
+
+## Comparison Mode
+
+When asked to compare packages:
+
+\`\`\`markdown
+# Comparison: A vs B vs C
+
+| Criteria | A | B | C |
+|----------|---|---|---|
+| Bundle size | X kb | Y kb | Z kb |
+| TypeScript | Native | @types | None |
+| Maintenance | Active | Stale | Active |
+| API style | Fluent | Declarative | Mixed |
+| [project-specific criteria] | ... | ... | ... |
+
+## Verdict
+Use [X] because [concrete reasons relevant to this project's stack and constraints].
+\`\`\`
+
+## Rules
+
+- **Official docs or nothing.** Don't cite a Medium post from 2021 as a source.
+- **Version matters.** Always note the version. APIs change between majors.
+- **Working examples only.** If you can't verify the code works, say so.
+- **Be opinionated.** If a package is garbage, say it's garbage and recommend an alternative. Don't be diplomatic about bad tools.
+- **Stay scoped.** Research what the ticket/task needs, not the entire package ecosystem. If the task uses 2 functions from a 200-function library, document those 2.
+`
+};
+export {
+  SFAG_PACKAGE_RESEARCHER
+};
+//# sourceMappingURL=sfag-package-researcher.js.map

package/dist/cli/templates/agents/content/research/sfag-package-researcher.js.map

@@ -0,0 +1 @@
+{"version":3,"sources":["../../../../../../src/cli/templates/agents/content/research/sfag-package-researcher.ts"],"sourcesContent":["/**\n * SFAG-Package-Researcher Agent Template v2\n *\n * Lean research agent. Find docs, extract what matters, report back.\n */\n\nimport type { AgentTemplate } from '../../../../commands/scaffold/agent-types.js';\n\nexport const SFAG_PACKAGE_RESEARCHER: AgentTemplate = {\n  name: 'sfag-package-researcher',\n  description: 'Research packages, APIs, and external docs',\n  triggerDescription: `Use this agent when you need to research external packages, libraries, or APIs before implementation. Gathers documentation, patterns, and gotchas.\n\n<example>\nContext: Ticket references a package the team hasn't used\nuser: \"Pesquisa como usar Stripe webhooks em Node.js antes de implementar\"\nassistant: \"Launching sfag-package-researcher to gather Stripe webhook docs and patterns.\"\n</example>\n\n<example>\nContext: Orchestrator needs research before delegating implementation\nuser: \"O ticket menciona usar Resend pra email — pesquisa primeiro\"\nassistant: \"Launching sfag-package-researcher to research Resend before implementation.\"\n</example>\n\n<example>\nContext: User wants to evaluate options\nuser: \"Compara Zod vs Yup vs Joi pra validação\"\nassistant: \"Launching sfag-package-researcher to compare validation libraries.\"\n</example>`,\n  model: 'sonnet',\n  color: 'magenta',\n  category: 'Research',\n  memory: 'project',\n  content: `# SpecForge Package Researcher Agent\n\nYou research external packages and APIs. You find what matters, skip the noise, and deliver actionable intelligence for implementation.\n\n## Process\n\n### 1. Search (official sources first)\n\\`\\`\\`\nSearch priority:\n1. Official docs site\n2. Official GitHub repo + README\n3. Official examples/tutorials\n4. npm/PyPI page for metadata (version, size, maintenance)\n\nSkip: Random blog posts, outdated tutorials, Stack Overflow answers from 3 years ago.\n\\`\\`\\`\n\n### 2. Extract (only what implementation needs)\n\nFor each package, gather:\n\n- **Install command** — exact, with version if it matters\n- **Minimal setup** — the shortest working example\n- **API surface** — the 3-5 functions/methods the ticket will actually use (not the full API reference)\n- **Configuration** — required config, env vars, secrets needed\n- **Error handling** — what errors does it throw? How to handle them?\n- **Gotchas** — breaking changes between versions, known bugs, things that don't work as expected\n- **Bundle/performance impact** — size, cold start implications, memory usage if relevant\n\n### 3. Report (structured, no prose)\n\nOutput format:\n\n\\`\\`\\`markdown\n# [Package Name] Research\n\n**Version:** x.y.z | **Last updated:** date | **Weekly downloads:** N\n\n## Install\n\\\\\\`\\\\\\`\\\\\\`bash\nnpm install package-name\n\\\\\\`\\\\\\`\\\\\\`\n\n## Setup\n\\\\\\`\\\\\\`\\\\\\`typescript\n// Minimal working example — copy-paste ready\n\\\\\\`\\\\\\`\\\\\\`\n\n## Key APIs (relevant to this task)\n- \\`functionA(params)\\` — what it does, what it returns\n- \\`functionB(params)\\` — what it does, what it returns\n\n## Configuration\n| Key | Required | Default | Description |\n|-----|----------|---------|-------------|\n| API_KEY | Yes | - | Your API key from dashboard |\n\n## Error Handling\n- \\`PackageError\\` — when X happens, handle with Y\n- Rate limits: N requests/min, returns 429\n\n## Gotchas\n- ⚠️ Version 3.x has breaking change in X\n- ⚠️ Does NOT work with ESM unless you configure Y\n- ⚠️ TypeScript types are incomplete for Z\n\n## Recommendation\n[Use it / Don't use it / Use alternative X instead] — because [concrete reason]\n\\`\\`\\`\n\n## Comparison Mode\n\nWhen asked to compare packages:\n\n\\`\\`\\`markdown\n# Comparison: A vs B vs C\n\n| Criteria | A | B | C |\n|----------|---|---|---|\n| Bundle size | X kb | Y kb | Z kb |\n| TypeScript | Native | @types | None |\n| Maintenance | Active | Stale | Active |\n| API style | Fluent | Declarative | Mixed |\n| [project-specific criteria] | ... | ... | ... |\n\n## Verdict\nUse [X] because [concrete reasons relevant to this project's stack and constraints].\n\\`\\`\\`\n\n## Rules\n\n- **Official docs or nothing.** Don't cite a Medium post from 2021 as a source.\n- **Version matters.** Always note the version. APIs change between majors.\n- **Working examples only.** If you can't verify the code works, say so.\n- **Be opinionated.** If a package is garbage, say it's garbage and recommend an alternative. Don't be diplomatic about bad tools.\n- **Stay scoped.** Research what the ticket/task needs, not the entire package ecosystem. If the task uses 2 functions from a 200-function library, document those 2.\n`,\n};\n"],"mappings":"AAQO,MAAM,0BAAyC;AAAA,EACpD,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;AAiGX;","names":[]}

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

@@ -0,0 +1,23 @@
+/**
+ * Agent Templates Module
+ *
+ * Defines all SpecForge agent templates for scaffolding to AI CLI tools.
+ */
+import type { AgentTemplate, AgentCategory } from '../../commands/scaffold/agent-types.js';
+/**
+ * Get all agent templates
+ */
+export declare function getAgentTemplates(): AgentTemplate[];
+/**
+ * Get a specific agent template by name
+ */
+export declare function getAgentTemplate(name: string): AgentTemplate | undefined;
+/**
+ * Get agent templates by category
+ */
+export declare function getAgentsByCategory(category: AgentCategory): AgentTemplate[];
+/**
+ * Get all agent template names
+ */
+export declare function getAgentNames(): string[];
+//# sourceMappingURL=index.d.ts.map

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

@@ -0,0 +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"}

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

@@ -0,0 +1,29 @@
+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_PACKAGE_RESEARCHER } from "./content/research/sfag-package-researcher.js";
+const AGENT_TEMPLATES = [
+  SFAG_ORCHESTRATOR,
+  SFAG_SPEC_CREATOR,
+  SFAG_TICKET_IMPLEMENTER,
+  SFAG_PACKAGE_RESEARCHER
+];
+function getAgentTemplates() {
+  return AGENT_TEMPLATES;
+}
+function getAgentTemplate(name) {
+  return AGENT_TEMPLATES.find((t) => t.name === name);
+}
+function getAgentsByCategory(category) {
+  return AGENT_TEMPLATES.filter((t) => t.category === category);
+}
+function getAgentNames() {
+  return AGENT_TEMPLATES.map((t) => t.name);
+}
+export {
+  getAgentNames,
+  getAgentTemplate,
+  getAgentTemplates,
+  getAgentsByCategory
+};
+//# sourceMappingURL=index.js.map

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

@@ -0,0 +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":[]}

package/dist/cli/templates/commands.d.ts

@@ -0,0 +1,17 @@
+/**
+ * Command Templates Module
+ *
+ * Defines all SpecForge slash commands with their full markdown content
+ * for scaffolding to AI CLI tools.
+ */
+import type { CommandTemplate } from '../commands/scaffold/types.js';
+export declare function getCommandTemplates(): CommandTemplate[];
+/**
+ * Get a specific command template by name
+ */
+export declare function getCommandTemplate(name: string): CommandTemplate | undefined;
+/**
+ * Get command templates by category
+ */
+export declare function getCommandsByCategory(category: string): CommandTemplate[];
+//# sourceMappingURL=commands.d.ts.map

package/dist/cli/templates/commands.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"commands.d.ts","sourceRoot":"","sources":["../../../src/cli/templates/commands.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;AAEH,OAAO,KAAK,EAAE,eAAe,EAAE,MAAM,+BAA+B,CAAC;AAWrE,wBAAgB,mBAAmB,IAAI,eAAe,EAAE,CAyDvD;AAED;;GAEG;AACH,wBAAgB,kBAAkB,CAAC,IAAI,EAAE,MAAM,GAAG,eAAe,GAAG,SAAS,CAE5E;AAED;;GAEG;AACH,wBAAgB,qBAAqB,CAAC,QAAQ,EAAE,MAAM,GAAG,eAAe,EAAE,CAEzE"}

package/dist/cli/templates/commands.js

@@ -0,0 +1,78 @@
+import { SF_INIT_CONTENT } from "./content/sf-init.js";
+import { SF_STATUS_CONTENT } from "./content/sf-status.js";
+import { SF_RESET_CONTENT } from "./content/sf-reset.js";
+import { SF_ANALYZE_BLOCKERS_CONTENT } from "./content/sf-blockers.js";
+import { SF_CONTEXT_CONTENT } from "./content/sf-context.js";
+import { SF_SEARCH_CONTENT } from "./content/sf-search.js";
+import { SF_COMMIT_CONTENT } from "./content/sf-commit.js";
+import { SF_HELP_CONTENT } from "./content/sf-help.js";
+function getCommandTemplates() {
+  return [
+    {
+      name: "sf-init",
+      description: "Initialize ticket system for a specification",
+      argumentHint: "[specification-id]",
+      content: SF_INIT_CONTENT,
+      category: "Setup"
+    },
+    {
+      name: "sf-context",
+      description: "View or switch working context",
+      argumentHint: "[project-or-spec-id]",
+      content: SF_CONTEXT_CONTENT,
+      category: "Setup"
+    },
+    {
+      name: "sf-status",
+      description: "Display implementation status with consolidated tools",
+      argumentHint: "[specification-id]",
+      content: SF_STATUS_CONTENT,
+      category: "Status"
+    },
+    {
+      name: "sf-analyze-blockers",
+      description: "Analyze blockers and dependency bottlenecks",
+      content: SF_ANALYZE_BLOCKERS_CONTENT,
+      category: "Status"
+    },
+    {
+      name: "sf-search",
+      description: "Search tickets by text, tags, or filters",
+      argumentHint: "<query>",
+      content: SF_SEARCH_CONTENT,
+      category: "Review"
+    },
+    {
+      name: "sf-reset",
+      description: "Reset ticket statuses with dependency awareness",
+      argumentHint: "[specification-id]",
+      content: SF_RESET_CONTENT,
+      category: "Utilities"
+    },
+    {
+      name: "sf-commit",
+      description: "Commit changes with SpecForge ticket metadata",
+      argumentHint: "[ticket-id]",
+      content: SF_COMMIT_CONTENT,
+      category: "Utilities"
+    },
+    {
+      name: "sf-help",
+      description: "Quick reference for all SpecForge commands",
+      content: SF_HELP_CONTENT,
+      category: "Utilities"
+    }
+  ];
+}
+function getCommandTemplate(name) {
+  return getCommandTemplates().find((t) => t.name === name);
+}
+function getCommandsByCategory(category) {
+  return getCommandTemplates().filter((t) => t.category === category);
+}
+export {
+  getCommandTemplate,
+  getCommandTemplates,
+  getCommandsByCategory
+};
+//# sourceMappingURL=commands.js.map

package/dist/cli/templates/commands.js.map

@@ -0,0 +1 @@
+{"version":3,"sources":["../../../src/cli/templates/commands.ts"],"sourcesContent":["/**\n * Command Templates Module\n *\n * Defines all SpecForge slash commands with their full markdown content\n * for scaffolding to AI CLI tools.\n */\n\nimport type { CommandTemplate } from '../commands/scaffold/types.js';\n\nimport { SF_INIT_CONTENT } from './content/sf-init.js';\nimport { SF_STATUS_CONTENT } from './content/sf-status.js';\nimport { SF_RESET_CONTENT } from './content/sf-reset.js';\nimport { SF_ANALYZE_BLOCKERS_CONTENT } from './content/sf-blockers.js';\nimport { SF_CONTEXT_CONTENT } from './content/sf-context.js';\nimport { SF_SEARCH_CONTENT } from './content/sf-search.js';\nimport { SF_COMMIT_CONTENT } from './content/sf-commit.js';\nimport { SF_HELP_CONTENT } from './content/sf-help.js';\n\nexport function getCommandTemplates(): CommandTemplate[] {\n  return [\n    {\n      name: 'sf-init',\n      description: 'Initialize ticket system for a specification',\n      argumentHint: '[specification-id]',\n      content: SF_INIT_CONTENT,\n      category: 'Setup',\n    },\n    {\n      name: 'sf-context',\n      description: 'View or switch working context',\n      argumentHint: '[project-or-spec-id]',\n      content: SF_CONTEXT_CONTENT,\n      category: 'Setup',\n    },\n    {\n      name: 'sf-status',\n      description: 'Display implementation status with consolidated tools',\n      argumentHint: '[specification-id]',\n      content: SF_STATUS_CONTENT,\n      category: 'Status',\n    },\n    {\n      name: 'sf-analyze-blockers',\n      description: 'Analyze blockers and dependency bottlenecks',\n      content: SF_ANALYZE_BLOCKERS_CONTENT,\n      category: 'Status',\n    },\n    {\n      name: 'sf-search',\n      description: 'Search tickets by text, tags, or filters',\n      argumentHint: '<query>',\n      content: SF_SEARCH_CONTENT,\n      category: 'Review',\n    },\n    {\n      name: 'sf-reset',\n      description: 'Reset ticket statuses with dependency awareness',\n      argumentHint: '[specification-id]',\n      content: SF_RESET_CONTENT,\n      category: 'Utilities',\n    },\n    {\n      name: 'sf-commit',\n      description: 'Commit changes with SpecForge ticket metadata',\n      argumentHint: '[ticket-id]',\n      content: SF_COMMIT_CONTENT,\n      category: 'Utilities',\n    },\n    {\n      name: 'sf-help',\n      description: 'Quick reference for all SpecForge commands',\n      content: SF_HELP_CONTENT,\n      category: 'Utilities',\n    },\n  ];\n}\n\n/**\n * Get a specific command template by name\n */\nexport function getCommandTemplate(name: string): CommandTemplate | undefined {\n  return getCommandTemplates().find(t => t.name === name);\n}\n\n/**\n * Get command templates by category\n */\nexport function getCommandsByCategory(category: string): CommandTemplate[] {\n  return getCommandTemplates().filter(t => t.category === category);\n}\n"],"mappings":"AASA,SAAS,uBAAuB;AAChC,SAAS,yBAAyB;AAClC,SAAS,wBAAwB;AACjC,SAAS,mCAAmC;AAC5C,SAAS,0BAA0B;AACnC,SAAS,yBAAyB;AAClC,SAAS,yBAAyB;AAClC,SAAS,uBAAuB;AAEzB,SAAS,sBAAyC;AACvD,SAAO;AAAA,IACL;AAAA,MACE,MAAM;AAAA,MACN,aAAa;AAAA,MACb,cAAc;AAAA,MACd,SAAS;AAAA,MACT,UAAU;AAAA,IACZ;AAAA,IACA;AAAA,MACE,MAAM;AAAA,MACN,aAAa;AAAA,MACb,cAAc;AAAA,MACd,SAAS;AAAA,MACT,UAAU;AAAA,IACZ;AAAA,IACA;AAAA,MACE,MAAM;AAAA,MACN,aAAa;AAAA,MACb,cAAc;AAAA,MACd,SAAS;AAAA,MACT,UAAU;AAAA,IACZ;AAAA,IACA;AAAA,MACE,MAAM;AAAA,MACN,aAAa;AAAA,MACb,SAAS;AAAA,MACT,UAAU;AAAA,IACZ;AAAA,IACA;AAAA,MACE,MAAM;AAAA,MACN,aAAa;AAAA,MACb,cAAc;AAAA,MACd,SAAS;AAAA,MACT,UAAU;AAAA,IACZ;AAAA,IACA;AAAA,MACE,MAAM;AAAA,MACN,aAAa;AAAA,MACb,cAAc;AAAA,MACd,SAAS;AAAA,MACT,UAAU;AAAA,IACZ;AAAA,IACA;AAAA,MACE,MAAM;AAAA,MACN,aAAa;AAAA,MACb,cAAc;AAAA,MACd,SAAS;AAAA,MACT,UAAU;AAAA,IACZ;AAAA,IACA;AAAA,MACE,MAAM;AAAA,MACN,aAAa;AAAA,MACb,SAAS;AAAA,MACT,UAAU;AAAA,IACZ;AAAA,EACF;AACF;AAKO,SAAS,mBAAmB,MAA2C;AAC5E,SAAO,oBAAoB,EAAE,KAAK,OAAK,EAAE,SAAS,IAAI;AACxD;AAKO,SAAS,sBAAsB,UAAqC;AACzE,SAAO,oBAAoB,EAAE,OAAO,OAAK,EAAE,aAAa,QAAQ;AAClE;","names":[]}

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

@@ -0,0 +1,7 @@
+/**
+ * SF-Analyze-Blockers Command Template
+ *
+ * Template for analyzing blockers and dependency bottlenecks.
+ */
+export declare const SF_ANALYZE_BLOCKERS_CONTENT = "# Analyze Blockers (SpecForge)\n\nAnalyze dependency bottlenecks and identify critical path tickets.\n\n## Task\n\n### 1. Get Implementation Data\n\n**MCP Calls:**\n```typescript\n// Read project config\nconst config = readFile('.specforge.json')\nconst specificationId = config.activeSpecification?.id\n\nget_specification({ specificationId })\nlist_epics({ specificationId })\nlist_tickets({ specificationId })\n```\n\n### 2. Analyze Dependencies\n\n**Logic:**\n- Build dependency graph\n- Calculate blocking relationships\n- Identify critical path\n- Find bottleneck tickets\n\n### 3. Display Analysis 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\nBLOCKER ANALYSIS\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\nSpecification: {title}\n\nCRITICAL PATH\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\nLength: {pathLength} tickets\nImpact: {blockedCount} tickets blocked\n\nE{n}-T{m} \u2192 E{n}-T{m} \u2192 E{n}-T{m} \u2192 ...\n\nHIGH-IMPACT BLOCKERS\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 {title} \u2502 Blocking {count} tickets\n  \u21B3 E{n}-T{m}, E{n}-T{m}, E{n}-T{m}\n\nBLOCKED 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 {title}\n  \u26A0 Waiting on: E{n}-T{m} ({status})\n\nRECOMMENDATIONS\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\u2022 Prioritize E{n}-T{m} to unblock {count} tickets\n\u2022 Review dependency chain for E{n}-T{m}\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- Identifies tickets blocking the most work\n- Shows critical path through implementation\n- Provides actionable recommendations\n";
+//# sourceMappingURL=sf-blockers.d.ts.map

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

@@ -0,0 +1 @@
+{"version":3,"file":"sf-blockers.d.ts","sourceRoot":"","sources":["../../../../src/cli/templates/content/sf-blockers.ts"],"names":[],"mappings":"AAAA;;;;GAIG;AAEH,eAAO,MAAM,2BAA2B,osHAgEvC,CAAC"}