feature-development

To implement new functionality reliably, use a disciplined workflow that structures discovery, codebase exploration, requirement clarification, and architecture design before writing code. This ensures integration points and backward compatibility are validated through user approval gates.

To clarify vague feature requirements, use a clarifying-first approach that prompts targeted questions to resolve ambiguities and edge cases. This resolves underspecified behavior and constraints before you commit to an architecture blueprint or implementation path.

Yes, you can use agent-assisted analysis to explore codebase patterns by instructing specialized explorer agents to gather key files. This deep context tracing helps identify behavior constraints and integration points needed for a validated implementation path.

To structure a feature implementation workflow with quality review, apply a lifecycle approach that emphasizes convention alignment, bug checks, and explicit issue triage. This includes a final quality review phase with a user decision step before code changes proceed.

You need a decisive architecture blueprint for adding new functionality when behavior, constraints, and backward compatibility are initially underspecified. It provides a validated implementation path after codebase exploration and requirement clarification phases are complete.

Feature planning does not work well without resolving edge cases first, as underspecified behavior leads to flawed architecture design. A clarifying-first approach prompts targeted questions to resolve ambiguities before proposing an implementation path.