Mental Model Discovery & Feature Implementation
Turn the requirement into change points: Requirement → Domain Logic → Validation → UI/API Contract → Persistence → Tests → Integration → Docs/Telemetry
Feature steps:
- Clarify the requirement and acceptance criteria.
- Reconstruct the current path.
- Find a similar feature and the project’s convention.
- Build an impact map and a file-based plan.
- Implement the smallest coherent change.
- Run targeted tests first, then broader tests.
- Review the diff for unintended changes.
- Update the mental model and documentation to reflect the new reality.
Architectural fit principle: Code that works but bypasses the project’s conventions and boundaries does not count as a complete Feature.
Implementing a Real Feature on an Existing Product
The complete cycle: Discovery → Problem Statement → Acceptance Criteria → Design → Implementation → Verification → Review → Release → Monitor → Feedback
A feature must be a usable vertical slice, not a collection of half-finished layers. In the PR, explain:
- Why this change is necessary;
- What has changed and what has been intentionally left unchanged;
- How it has been tested;
- What the risks, rollout plan, migration, and rollback strategy are;
- A log, screenshot, or API sample if needed.
Definition of Done: Code is written, tests pass, acceptance criteria are confirmed, review is complete, necessary documentation and telemetry are updated, and the behavior is ready to be released.