feature
Refine an accepted idea into a validated, approved OpenSpec-compatible change without imposing vendor-specific governance or task tracking.
SKILL.mdskills/feature/SKILL.md
GitHubFeature
Create an executable change definition. OpenSpec-compatible artifacts are the interchange format; this skill is not an OpenSpec vendor workflow.
Stages
- Load the request and any exploration record.
- Discover repository instructions, active changes, relevant capabilities, implementation surfaces, tests, and dependencies.
- Resolve genuine product and architecture decisions. Ask only for judgment that repository or Context7 evidence cannot settle.
- Define scope, non-scope, actors, behavior, edge cases, user actions, dependencies, touched capabilities, migration needs, and acceptance evidence.
- Draft
proposal.md, requirement/capability deltas, optionaldesign.md, and orderedtasks.mdunder the repository's change directory. - Make task dependencies explicit. Do not add universal DB/API/UI/E2E phases.
- Validate artifact structure, requirement scenarios, task readiness, paths, and dependency consistency.
- Present the change for approval. Do not begin implementation before approval.
Required quality
Every material requirement needs observable behavior and failure/edge scenarios. Every unresolved human action is either resolved during authoring or represented as a dependent proposal boundary. Out-of-scope behavior is explicit. Tasks include scope and verification instructions.
Do not include
Beads, vendor-specific issue IDs, mandatory ambiguity lenses, constitution audits, telemetry, or hidden governance passes. Those belong to separate skills when explicitly requested.