spec-write

To create feature requirement specs across multiple feature requests, you scaffold per-FR frontmatter and generate files under specs/frs. This enforces bimodal identity rules, generates AC prefixes, and validates post-write shapes to maintain traceability and consistency across documentation.

Bimodal identity handling in feature spec frontmatter allows identifiers to function in two modes: using tracker-mode IDs for integrated workflows or generating short ULIDs for mode:none workflows. This ensures consistent spec traceability regardless of external tracker dependencies.

Validating feature spec frontmatter after writing requirements involves applying post-write shape validation. This verifies that frontmatter conforms to defined rules, ensuring milestone attachments and workspace bindings align correctly with the generated feature specifications.

Feature spec documentation works without tracker integration by utilizing mode:none workflows. This configuration uses short ULIDs instead of tracker-mode IDs for feature request identification, enabling spec creation and maintenance independently of external tracker systems.

The best way to maintain testing specs and planning milestones across multiple FRs is through automated end-to-end documentation workflows. These workflows enforce frontmatter shapes, generate acceptance criteria prefixes, and integrate workspace bindings with milestone attachments to ensure consistency and traceability.

Spec generation requires workspace binding and milestone attachment checks to enforce proactive consistency and traceability across feature requests. These checks ensure that generated frontmatter aligns with bimodal identity rules and tracker gating rules, preventing duplicate imports and structural misalignment.