Ankit1598 PRD Workflow
Local-only — no GitHub issues or PRs. All outputs go to .artifacts/.
Phase 1 — Discovery & PRD
- Ask for a detailed problem description + any solution ideas
- Explore the codebase to validate assertions and understand the current architecture
- Interview relentlessly using the grill-me pattern — one decision-tree branch at a time — until shared understanding is reached
- Sketch major modules to build or modify; identify deep modules (small interface hiding large implementation — more testable, more AI-navigable)
- Quality gate — every requirement must be concrete and measurable:
- Never: "fast", "easy", "intuitive", "seamless", "better"
- Always: "returns results within 200ms for 10k records", "achieves ≥85% Precision@10 in benchmark", "reduces error rate below 1%"
- Write PRD using the schema in REFERENCE.md
- Output:
.artifacts/features/<entityName>/guides/PRD_<FEATURE_NAME>.md
Phase 2 — Phased Implementation Plan
- Identify durable architectural decisions upfront — these stay stable across all phases:
- Route structures / URL patterns
- Database schema shape and key data models
- Authentication / authorization approach
- Third-party service boundaries
- Break into vertical slices (tracer bullets) — each phase cuts through ALL layers end-to-end (schema + API + UI + tests). Never horizontal layer-by-layer.
- Present proposed phases — for each: title, user stories covered, what to build, acceptance criteria, commit checkpoint
- Quiz the user: does the granularity feel right? Too coarse / too fine? Merge or split?
- Finalize only after approval
- Output:
.artifacts/features/<entityName>/guides/IMPLEMENTATION_PLAN_<FEATURE_NAME>.md - Durable choices made during planning → decision-records under
.artifacts/decisions/ - After a phase ships → suggest commit via git-commit (checkpoint = hint; live tree wins) → artifacts-upkeep
Commit checkpoints (required on every phase)
- Default: one checkpoint at the end of each phase (after acceptance criteria pass).
- Split into 2+ checkpoints only if the phase has clearly independent shippable bits.
- Record: suggested subject hint, likely path buckets, “do not mix later-phase files.”
- Checkpoint is planning guidance only — at ship time always run git-commit for exact
git add/ message from the working tree. Keep the checkpoint’s staging boundary; refine type/subject/paths as needed.
Output Naming
.artifacts/features/auth/guides/PRD_SIGN_IN_FLOW.md
.artifacts/features/auth/guides/IMPLEMENTATION_PLAN_SIGN_IN_FLOW.md
.artifacts/features/notifications/guides/PRD_PUSH_NOTIFICATIONS.md
Full PRD template and implementation plan template → see REFERENCE.md. Placement → dev-artifacts. Interview pattern → grill-me.