Feature Workflow
Two complete feature plans that the planning agent produced from one-line briefs. Each is the literal markdown written to features/feature-XXX.md by /hypr:plan.
What a feature plan contains
The plan is the contract between a one-line ask ("add version comparison") and the implementation. Sections, in order:
- Status & timeline — current phase, started/estimated dates, priority.
- Feature overview — what is being built and why.
- Current system analysis — what exists, what's missing.
- Implementation plan & progress — phased chunks, each sized to fit in a single session (< 2 hrs).
- Acceptance criteria — checklist that decides "done".
- Testing strategy, rollback plan, open questions, progress log.
The numbering is deliberate: each chunk has a stable identifier so the implementation agent and review agent can refer to a specific scope without re-reading the whole plan.
Feature 001 — Version history
Adding a versioned change-log to a content app: archive, comparison, rollback, and version-based shareable URLs. Both backend (DB schema, API) and frontend (versions list, comparison view) chunks. Estimated 13–18 hours across 4 phases.
Highlights from the plan:
- Phase 1 — schema additions (
archivedAt,previousVersionId,versionNotes), service-layer enforcement of the one-active-version rule. - Phase 2 — comparison API + diff renderer.
- Phase 3 — rollback flow (audit trail + UI confirmation).
- Phase 4 — shareable version URLs and access checks.
Full file: 001-version-history.md on GitHub (297 lines).
Feature 002 — CI optimization
Restructuring a CI pipeline so unrelated suites run in parallel. Shows how the planning agent treats build-system work — fewer phases, more emphasis on rollback and re-runnability.
Highlights:
- Audit current job graph; identify chains that don't need to be sequential.
- Split into independent workflows with clear artifact boundaries.
- Add a smoke job that fans-in before the deploy gate so failures are caught at the merge point, not after deploy.
Full file: 002-ci-optimization.md on GitHub (145 lines).
Related
- Feature Development Flow — the workflow these plans flow through.
/hypr:plan— generates these plans./hypr:implement— executes a single chunk from the plan./hypr:build-chunk— implement + review loop until a chunk is approved.