x-create-capability

To decompose a product into capabilities, you generate 3–7 capability artifacts with explicit RNF inheritance and no-relax markers for downstream planning. This enforces structured allocation by capturing non-negotiable constraints before feature definition.

RNF inheritance in capability decomposition propagates non-negotiable requirements from the product level down to individual capabilities using no-relax markers. It ensures these constraints are explicitly documented and cannot be loosened during downstream feature planning.

You generate capability artifacts after a product is defined and before creating features. This intermediate decomposition step produces 3–7 capability files to structure planning, enforce RNF constraints, and optionally seed a second capability stub for further breakdown.

Decomposing a product into capabilities requires the --capability-id flag and either --capabilities or --auto-decompose. These flags trigger generation of capability artifacts containing an Inherited RNFs section that documents non-negotiable constraints.

Yes, you can automatically seed further decomposition by optionally generating a second capability stub. This stub provides a starting point to break down capabilities into finer-grained artifacts for downstream feature planning and allocation.

Generated capability artifacts use the Markdown format, outputted as ai/capabilities/capability-NNNN.md files. Each artifact includes an Inherited RNFs section to explicitly document the non-negotiable RNF constraints assigned to that specific capability.