pm-feature-design

Just-in-time technical design creates implementation-ready documentation for individual features by enriching feature cards with business rules, acceptance criteria, and sequence diagrams before development begins. This prevents vague specifications and premature architecture decisions.

Feature specification alignment identifies files to modify and generates Mermaid sequence diagrams to match new functionality with the existing codebase. It interrogates requirements to surface edge cases and finalize rules for build handoffs.

Documenting acceptance criteria and business rules enriches feature cards with entity guard conditions, subtasks, and implementation-ready design details. This process finalizes decision models and prepares handoff packages for builders and reviewers.

Yes, generating sequence diagrams for feature design requires feature cards and domain registers to produce implementation-ready documentation. These inputs drive the discovery and validation process to align designs with business rules.

Use just-in-time feature design when you need to prevent premature architecture decisions and bridge the gap between product requirements and implementation. It applies to workflows requiring feature specifications, acceptance criteria, and build handoffs.

Just-in-time technical design focuses on individual features within a development stripe, requiring feature cards and domain registers as prerequisites. It is not intended for comprehensive upfront system architecture planning across multiple features simultaneously.