writing-specs

Automate feature spec generation by initiating a structured workflow that creates FEATURES.md entries, defines acceptance criteria, maps NFRs, and tracks delta changes across the feature lifecycle. This enforces spec health checks and contract protection.

Delta tracking for feature specs records incremental changes and additive updates across planning, in-progress, and shipped stages. You need it when evolving shipped features with justification markers to enforce contract rules and audit spec health.

Create migrations for updated features by applying additive changes with justification markers, enforcing contract protection rules, and coordinating with framework tooling. This guarantees structured spec evolution while tracking deltas and maintaining spec health checks.

Yes, you can manage non-functional requirements within the feature planning workflow. The system integrates NFR mappings, enforces spec health checks, and tracks delta changes alongside acceptance criteria and migration creation.

The best way to structure feature specs is using an automated workflow with ID management (F-XXXX), FEATURES.md entries, acceptance criteria, and NFR integration. This enforces contract rules, tracks deltas, and maintains spec health across the lifecycle.

Yes, the spec-writing workflow supports auditing shipped features by applying additive changes with justification markers. It enforces contract protection, tracks deltas, and coordinates migration creation to ensure structured spec evolution.