Workflow

flowchart LR
A((Start))
B{New project?}
C[Discuss requirements with AI]
D[Discuss feature/scope with AI]
E([Generate PRD & Dev Plan])
F([Generate Dev Plan])
G([Create tickets])
H([Review ticket])
M{All good?}
I([Implement ticket])
J[Test/Validate]
K([Update ticket])
N([Defer ticket])
L([Commit ticket])
A-->B
B-->|Yes|C
B-->|No|D
C-->E
D-->F
E-->G
F-->G

subgraph Design["Design Phase"]
C
D
E
F
G
end

subgraph Implementation["Implementation Phase"]
H
I
J
M
K
N
L
end

G-->H-->I-->J-->M
M-->|Yes|K
M-->|No|I
M-->|Defer|N
K-->L
N-->L
L-->H

Loading

Simplified Version

Generate PRD & Dev Plan

• <requirement_discussion_conversation_history/> Based on our discussion, please create a detailed PRD and a Development Plan with as much context as possible. Save them as Markdown files and provide download links.

Create Tickets (from PRD + Dev Plan)

• Please review the <PRD_DOC> and <DEV_PLAN_DOC>, then break down the development plan into small, easy-to-test, and actionable tickets. Each ticket should include a summary, rationale (why), scope, out-of-scope items, acceptance criteria, implementation steps, testing/validation instructions, and any dependencies or related tickets. Save the tickets as Markdown files in the docs/tickets/ folder.

Implement Ticket

• Please start working on <TICKET_DOC>. If anything is unclear, ask for clarification.

Update Ticket

• <implementation_conversation_history/> Please update ticket <TICKET_DOC> and mark it as done. Also, update any dependent tickets to clarify the new code dependencies, which will provide better context for anyone who works on them in the future.

Defer Ticket

• <implementation_conversation_history/> We encountered an issue while implementing this ticket. <ERROR_LOG> It appears to be more complex than originally thought and may require further research. Please defer this ticket and update any related tickets accordingly.

Commit Ticket

• <implementation_conversation_history/> Let's commit our progress.

---

Full Version

Generate PRD & Dev Plan

<requirement_discussion_conversation_history/>

You are a senior staff-level engineer + product lead.

# Goal: From our discussion, produce a complete **PRD** and **Development Plan** with full context.

If anything material is missing, ask up to 3 targeted questions. If you can proceed, make reasonable assumptions and list them in an **Assumptions** section.

# OUTPUT

- Create two markdown files with the exact filenames:
	- `PRD.md`
	- `DEV_PLAN.md`

- In `PRD.md` include: Title, Problem, Goals/Non-Goals, Users/Personas, Requirements (functional + non-functional), Constraints, Risks, Open Questions, Milestones, Success Metrics, Analytics/Telemetry, Accessibility/Internationalisation, Privacy/Security, and a Glossary.

- In `DEV_PLAN.md` include: Architecture overview, Component breakdown, Data model, API surface, State management, Error handling, Observability, Test strategy (unit/int/e2e), Release plan, Rollout/rollback, and a week-by-week timeline.

- Cross-link the files with relative links.

- Provide **download links** to both files.

# STYLE

- Be specific. Use numbered lists, tables, and diagrams (Mermaid) where useful.

- Prefer present tense, imperative voice.

- Keep sections skimmable with crisp headings and bullets.

Create Tickets (from PRD + Dev Plan)

You are a methodical tech lead creating a ticket set.

Inputs:
- PRD: <PRD_DOC_PATH or pasted content>
- DEV PLAN: <DEV_PLAN_DOC_PATH or pasted content>

Task:
- Break the development plan into small, independently testable, actionable tickets.

Rules:
- One markdown file **per ticket** in `docs/ticket/`.
- Filename pattern: `docs/ticket/T-<NNN>-<kebab-title>.md` (e.g., `T-012-setup-ci.md`).
- Also generate an index at `docs/ticket/README.md` with a table listing: ID, Title, Type, Priority, Estimate, Status, Dependencies.

Each Ticket MUST include (in this order):
1) **ID**: T-<NNN>
2) **Title**: short, imperative
3) **Type**: feature | chore | bug | spike | doc
4) **Priority**: P0–P3
5) **Estimate**: points or hours
6) **Summary**
7) **Why (Goal / outcome)**
8) **Scope (In / Out of scope)**
9) **Requirements**
10) **Acceptance Criteria** (Gherkin-style where possible)
11) **Implementation Steps** (ordered, minimal)
12) **Test/Validation Plan** (unit/int/e2e + manual)
13) **Observability** (logs, metrics, alerts)
14) **Dependencies / Related Tickets**
15) **Risks & Mitigations**
16) **Rollback Strategy**
17) **References** (links to PRD/DEV_PLAN sections)

Conventions:
- Keep tickets ≤ 1 day of work where possible.
- If a task exceeds 1 day, split it.

Implement Ticket

You are a senior IC implementing a single ticket.

Input:
- Ticket: <TICKET_DOC_PATH or pasted content>

Process:
1) **Restate Understanding**: brief recap of the ticket and goal.
2) **Assumptions**: list any assumptions; if blockers, ask up to 3 targeted questions. If reasonable to proceed, continue and note assumptions in the ticket.
3) **Plan**: minimal plan (steps, files to touch, tests to add).
4) **Changes**: provide a git-apply-able unified diff (patch) OR explicit code blocks per file with full paths.
5) **Tests**: add/update tests; include commands to run them.
6) **Validation**: CLI steps to verify behavior; include expected outputs.
7) **Observability**: logs/metrics added or verified.

Constraints:
- Keep changes small and reversible.
- No secrets or real credentials. Use placeholders and `.env.example`.

Output:
- Code changes (diff or file blocks)
- Updated/created docs
- Notes on any follow-ups or new tickets required

Update Ticket

<implementation_conversation_history/>

You are updating ticket state and cross-refs.

# Inputs:

- Ticket to update: <TICKET_DOC_PATH>
- Optional: related tickets list

# Tasks:

1) **Mark Status**: set to Done (use a status field at the top).
2) **What changed**: 3–6 bullet summary with links to commits/PRs (or placeholders).
3) **Acceptance Criteria**: mark each item as ✅/❌ with notes.
4) **Dependencies**: update related tickets with precise notes: which module/API/function they now depend on and why, link anchors where relevant.

5) **Artifacts**: link to generated docs, diagrams, or test reports.

Defer Ticket

<implementation_conversation_history/> We encountered an issue <ERROR_LOG> while implementing this ticket. It appears to be more complex than originally thought and may require further research. Please defer this ticket and update any related tickets accordingly.

Commit Ticket

<implementation_conversation_history/>

You are preparing a clean commit for the work tied to a ticket.

# Input:
- Ticket: <TICKET_ID and/or TICKET_DOC_PATH>

# Rules:
- Use Conventional Commits.
- Include the ticket ID in the subject and footer.
- Summarise what and why in the body; reference any follow-ups.

# Output:
- A suggested commit message block.
- The exact git commands.

# Template:

## Subject:
<type>(<scope>): <succinct change> [<TICKET_ID>]

## Body:
- Why: <concise rationale>
- What: <key changes>
- Tests: <how verified; commands; coverage notes>
- Notes: <breaking changes? migrations? feature flags?>

## Footer:
Refs: <TICKET_ID>
Co-authored-by: <Name <email>> (optional)

# Example:

feat(auth): add passwordless email login [T-014]

Why: Reduce sign-in friction and unify mobile/web flows.
What: adds /auth/magic-link endpoint, token verification, email templates
Tests: `pnpm test:unit`, `pnpm test:e2e` all green
Notes: env `MAGIC_LINK_SECRET` required; feature-flagged

Refs: T-014

# Commands:

git add -A
git commit -m "<paste subject line>" -m "<paste body and footer>"