feature-design

To turn a feature idea into an implementation plan, you need a guided workflow that explores the codebase, records design decisions, and generates phased tasks with exact file paths and complete code snippets. This process prevents scope creep and ensures mechanically verifiable execution.

Feature design translates requirements into executable plans, while decision records capture the rationale behind those choices. Using SeleneDB to store decisions enables cross-session traceability, preventing knowledge loss and ensuring team alignment before code execution.

Creating a phased implementation plan with verification and rollback strategies involves generating exact file-level tasks, complete code snippets, and dependency graphs. The plan must enforce non-goals and produce test commands to verify code correctness against repository constraints.

Yes, you can use SeleneDB to track design decisions by creating sessions and recording Decisions, Documents, and Milestones. This integration links research directly to plans, enabling provenance and cross-session recall for medium-to-large software features.

Yes, this feature planning workflow supports code generation for an existing repository by exploring the codebase context, generating exact file paths, and writing complete code for each task. It verifies the generated plan against the repository constraints before handoff.

You should use a formal feature design workflow over conversational planning when starting medium-to-large features that require strict team alignment, decision traceability, and code-level correctness before execution. It enforces non-goals and produces mechanically verifiable tasks.