Guide
Add A New Feature
A practical pattern for extending an existing codebase without drifting scope.
For iterative work inside an existing repository, use enhance or create depending on how new the behavior really is.
The key rule is to keep the change scoped to the confirmed problem and avoid silently inventing new product policy.
Suggested Pattern
- Start with repository inspection and affected surface mapping.
- Choose one workflow and one primary subagent role.
- Load only the stack-relevant skills.
- Keep unrelated files untouched unless they are required dependencies.
- Run
check, and escalate toverifyif the feature crosses subsystem boundaries.