software-factory

Software Factory

Software Factory is an AI-native SDLC method for connecting product intent, technical intent, and implementation work in one traceable workflow.

This skill equips you to use the Software Factory MCP effectively and guides you through reliable, traceable Work Order execution in this repository.

Records

• The Knowledge Base holds the project's documents and files, such as research, meeting notes, and design artifacts.
• Requirements describe the system from an external perspective: what it must do for its users and why.
• Blueprints describe the system from an internal perspective: its components, contracts, and architecture.
• Work Orders describe delivery: the implementable scope of a change, its exclusions, and the requirements and blueprints it connects to.
• Feedback is requests and reports submitted by the product's users.
• Themes group feedback items that share a common root cause, so they can be triaged together and addressed in one Work Order.

Record authoring

Before you create or change a Knowledge Base document, requirement, blueprint, Work Order, feedback item, or theme, read the project's current writing rules for that kind of record through the Software Factory MCP. Call list_skills to find the writing rules for that kind of record, then call read_skill on that skill and read any child skill it points you to. Write the record exactly as those rules describe. If the Software Factory MCP is unavailable, stop and tell the user.

During implementation, read every referenced Blueprint through the Software Factory MCP before coding, including @… mentions and links.

Routing

Work Order Execution

Follow the execution process for every Work Order. Finish every checklist item in one of two states: checked complete with [x], or marked [SKIP] with a skip reason. An unchecked item is an execution failure.

Follow execution/execute-work-order.md for single Work Orders and multi-Work-Order queues, and read the related files in execution/ when that guide routes to them. The execution files record how the work was done; the Software Factory MCP writing rules govern the records themselves.

The checklist is a living harness-engineering artifact. Teams evolve it with the exact commands, checks, screenshots, migrations, fixtures, seed data, CI gates, and review rituals that make agentic programming reliable in their codebase.

Commit, push, open a pull request, or merge only when the user or the repository workflow asks for it.