Idea-to-Tickets SOP
Purpose: Standard operating procedure for the idea-to-tickets skill. Defines template selection, phase breakdown rules, and Linear creation checklist.
Reference: .cursor/skills/idea-to-tickets/SKILL.md
Template selection
| Signal | Template |
|---|---|
| Product/feature for client, staged milestones (POC/MVP/V1) | PRD (standards/02-writing/PRDs/prd-template.md) |
| Feature, enhancement, non-trivial change to existing project | Lightweight Design Doc (standards/06-technical-planning/Lightweight Design Doc Template.md) |
| New platform, major migration, broad architectural impact | Full TDD (Data or AI & Platform) |
Default: Lightweight Design Doc when scope is unclear.
Phase breakdown rules
- 3–6 implementation phases
- Each phase: name, scope (bullets), success criteria
- Follow pattern from
knowledge/plans/per-user-clockify-platform-2026.md - Phases should have clear boundaries (no overlap)
Ticket creation rules
- Size: 0.5–2 days each; no phase-sized tickets
- Phase labels:
Phase 1,Phase 2, etc. - blockedBy: Link dependencies (e.g. Ticket 2 blockedBy Ticket 1)
- AI vs human:
ai-assignableorhuman-onlyperstandards/03-knowledge/engineering/setup/linear-labels-ai-human.md - State: First ticket(s) in “ToDo” or “Ready for Work”; not all in Backlog
- Description: Use template from
standards/04-prompts/tickets/linear-ticket-generation-from-transcript.md
Linear project/ticket creation checklist
Before creating:
- Searched Linear for duplicates
- User confirmed “create Linear”
- Team resolved (asked or inferred)
- Plan saved to
knowledge/plans/{slug}-{year}.md
When creating tickets:
- Phase labels applied
- blockedBy set for dependencies
- ai-assignable or human-only label applied
- First ticket(s) moved to ToDo
- Description uses required template
Dry-run mode
User can request “preview only” or “dry run”: output plan + ticket table as markdown without calling Linear. Useful for review before creation.