software-factory

name	software-factory
description	Run a hands-free SDD software factory from user intent. Use for /factory. Converts intent into specs, plans, task groups, bounded delegation, model routing, verification, progress logging, and approval gates.

Software Factory Skill

Goal

Convert one user intent into verified implementation progress with minimum human input, minimum token cost, and explicit approval gates.

Source of Truth

• Product truth: .specs/
• Execution truth: .tasks/
• Repo rules: AGENTS.md
• Proof: tests and verification output

Runtime Roles

Use only:

• Main Integrator
• Explorer
• Worker
• QA

Architecture review is temporary and only used after repeated failure or cross-cutting conflict.

Pipeline

1. Triage intent.
2. Identify or create feature slug.
3. Read repo rules and product specs.
4. Create or update .specs/{feature}/spec.md.
5. Create or update .specs/{feature}/plan.md.
6. Create or update .specs/{feature}/tasks.md.
7. Create or update .specs/{feature}/validation.md.
8. Create or update .tasks/{date}-{feature}-TASKS.md.
9. Pick next unblocked P0 task.
10. Use Explorer only if file ownership is unclear.
11. Assign one Worker to one bounded task.
12. Run QA.
13. Update task status and Progress Log.
14. Stop at human approval gate.

Cost Rules

• Use cheapest capable model.
• Do not spawn overlapping agents.
• Do not run architecture review unless blocked.
• Do not re-read old logs unless they are dependencies.
• Summarize large artifacts before passing to workers.
• Stop after one verified task unless the user explicitly requests full auto-run.

Safety Rules

• Never merge without approval.
• Never delete data without approval.
• Never change secrets, auth, billing, or production config without approval.
• Never hide failed verification.
• Never mark done without proof.

Output

Always return:

• Intent summary
• Files created or updated
• Task executed
• Agent/model route used
• Verification result
• Cost-control notes
• Next recommended command