From software-factory
Skills for coding agents to use the 8090 Software Factory—requirements, blueprints, work orders, and structured work order execution, with implementation plans, review, and verification. This skill is a directory: read it first, then follow the relevant guide or execution process.
How this skill is triggered — by the user, by Claude, or both
Slash command
/software-factory:software-factoryThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Software Factory is an AI-native SDLC method for connecting product intent, technical intent, and implementation work in one traceable workflow.
execution/execute-work-order.mdexecution/review-phase.mdexecution/scripts/checklist-template.mdexecution/scripts/context-template.mdexecution/scripts/implementation-plan-template.mdexecution/scripts/init-wo-execution.shexecution/scripts/review-log-template.mdexecution/scripts/update-context-index.shexecution/writing-implementation-plans.mdguides/blueprint-writing-guide.mdguides/requirements-writing-guide.mdguides/work-order-writing-guide.mdSoftware Factory is an AI-native SDLC method for connecting product intent, technical intent, and implementation work in one traceable workflow.
This portable skill is for writing Software Factory records and executing Work Orders headlessly in any repository. It does not assume access to a hosted Software Factory service, private repository automation, or repository-specific review skills. When project tools are available, use them; otherwise, use the files and templates in this skill as the execution system of record.
Requirements describe the system from an external perspective.
Read guides/requirements-writing-guide.md when writing or revising requirements.
Blueprints describe the system from an internal perspective.
component blocks define runtime nodes; relationship paragraphs describe data, contracts, and control flow.Read guides/blueprint-writing-guide.md when writing or revising blueprints. During implementation, follow referenced Blueprints—including @… mentions and links resolved via MCP—before coding so the full component graph is understood.
Work Orders describe delivery intent: implementable scope, exclusions, connected requirements, connected blueprints, and acceptance-test expectations.
Read guides/work-order-writing-guide.md when creating or updating Work Orders.
| Task | Read |
|---|---|
| Executing one Work Order | execution/execute-work-order.md |
| Executing multiple Work Orders | execution/execute-work-order.md |
| Writing an implementation plan during execution | execution/writing-implementation-plans.md |
| Running the review phase | execution/review-phase.md |
| Initializing an execution directory | execution/scripts/init-wo-execution.sh |
| Updating execution context | execution/scripts/update-context-index.sh |
| Writing or revising requirements | guides/requirements-writing-guide.md |
| Writing or revising blueprints | guides/blueprint-writing-guide.md |
| Creating or updating Work Orders | guides/work-order-writing-guide.md |
Work Order executions must follow the execution process every time. Every checklist item must be checked complete with [x] or explicitly marked [SKIP] with a skip reason. Do not treat an unchecked item as implied, optional, or complete.
Follow execution/execute-work-order.md for single Work Orders and multi-Work-Order queues. Read the related files in execution/ when that guide routes to them.
The checklist is intentionally a living harness-engineering artifact. Teams should 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.
Version-control handoff is user-directed. Do not assume when to commit, push, open a PR, or merge unless the user or repository workflow specifies it.
Provides behavioral guidelines to reduce common LLM coding mistakes, focusing on simplicity, surgical changes, assumption surfacing, and verifiable success criteria.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub 8090-inc/software-factory-plugin --plugin software-factory