product-capability

Topics in the source

• Product Capability
• When to Use
• Canonical Artifact
• Non-Negotiable Rules
• Inputs
• Core Workflow
• 1. Restate the capability
• 2. Resolve capability constraints

This skill turns product intent into explicit engineering constraints. Use it when the gap is not "what should we build?" but "what exactly must be true before implementation starts?" A PRD, roadmap item, discussion, or founder note exists, but the implementation constraints are still implicit A feature crosses multiple services, repos, or teams and needs a capability contract before coding Product intent is clear, but architecture, data, lifecycle, or policy implications are still fuzzy Senior engineers keep restating the same hidden assumptions during review You need a reusable artifact that can survive across harnesses and sessions If the repo has a durable product-context file such as PRODUCT.md, docs/product/, or a program-spec directory, update it there. If no capability manifest exists yet, create one using the template at: docs/examples/product-capability-template.md The goal is not to create another planning stack. The goal is to make hidden capability constraints durable and reusable. Do not invent product truth. Mark unresolved questions explicitly. Separate user-visible promises from implementation details. Call out what is fixed policy, what is architecture preference,

This is an excerpt. Refer to the complete source and its current requirements.