Feature Workflow
Every new product feature follows this pipeline. Identify the next step, verify its prerequisite, run it, commit.
Why
A feature is built on intent and context, never on guesses.
The Pipeline
- Plan (Always Work From A Plan).
- Functional doc at
docs/features/<feature>.md(Feature Template). - The laws a project adopted are checked against the feature, in a step of their own.
- Spec at
docs/features/<feature>.spec.md(Feature Spec Template). - E2E tests, failing first (E2E Test Conventions).
- Implement use case by use case, in mock state (Develop Against Mocks).
- Regression-test the affected area.
- Proof: a screenshot, a video, a test run or whatever fits, that tells the director the feature is done and lets the director verify it. Proof the director cannot check is no proof (Reels And Video Proof).
Small steps keep the focus.
Doc, spec and e2e steps are observation only - no production-code edits (Non-Destructive Documenting And Test Automation).
Commit at each step boundary on the work's branch (Commits). Never blend steps. The steps land on main together, green (Main Stays Green, Work Stays Clean). If a prerequisite is missing, park and recurse (Backward-Trace Missing Prerequisites).