Idea-to-Tickets Skill Plan
Date: 2026-03-07
Status: In progress
Linear: AI-833
Goal
A skill that walks an idea, long prompt, or set of ideas through the Brainforge process: Idea → Plan → Phases → Project → Tickets. The skill acts as a structured guide, not a one-shot generator—users can stop at any stage or continue to Linear creation.
Current Process (What Exists)
| Stage | Artifacts | References |
|---|---|---|
| Idea | Raw input | User provides |
| Plan | PRD, TDD, or Lightweight Design Doc | standards/02-writing/PRDs/prd-template.md, standards/06-technical-planning/ |
| Phases | Numbered phases with scope | knowledge/plans/per-user-clockify-platform-2026.md (sections 5–6) |
| Project | Linear project | Linear MCP save_project, .cursor/rules/linear-mcp-ticket-standards.mdc |
| Tickets | Linear issues | standards/04-prompts/tickets/linear-ticket-generation-from-transcript.md |
Skill Design
Trigger phrases
- “Walk this idea through to tickets”
- “Turn this into a plan and Linear tickets”
- “Help me go from idea to plan to phases to tickets”
- “I have an idea / long prompt / set of ideas—take it through the full process”
- “Create a plan and tickets from this”
Core workflow (5 stages)
- Idea capture — Extract problem, goal, scope; ask clarifying questions; output refined one-pager
- Plan — Choose template (PRD/TDD/Lightweight); draft section-by-section; save to
knowledge/plans/{slug}-{year}.mdfor a single file, orknowledge/plans/{initiative-folder}/withREADME.mdplus related.mdfiles when one initiative has multiple documents (seeknowledge/plans/README.md§ Structure). - Phases — Break into 3–6 implementation phases with clear boundaries
- Project — Create Linear project via MCP
- Tickets — Create small tickets (0.5–2 days each) with phase labels, blockedBy, ai-assignable/human-only labels
Label scheme: AI vs human
| Label | Meaning | When to use |
|---|---|---|
| ai-assignable | AI can implement; human reviews before close | Implementation tickets with clear acceptance criteria |
| human-only | Human must do this; do not assign to AI | Security review, stakeholder sign-off, subjective UX |
Filter for AI work: label:ai-assignable in Linear.
Related skills
1. Document council (stress-test for docs)
Council-style multi-agent review. Personas depend on doc type; Stakeholder persona always included (dynamic: client/internal/partner). Stakeholder focus: clarity without full context, no glaring mistakes, fair assumptions.
Doc types: PRD, TDD, SOW, Offer, SOP, Campaign brief, Client deliverable, Runbook, Internal proposal.
2. Linear status sync
When tickets move to Done → update project progress → update initiative status.
Deliverables
| Deliverable | Path |
|---|---|
| Idea-to-tickets skill | .cursor/skills/idea-to-tickets/SKILL.md |
| Idea-to-tickets SOP | standards/04-prompts/planning/idea-to-tickets-sop.md |
| Label scheme (playbook) | standards/03-knowledge/engineering/setup/linear-labels-ai-human.md |
| Document council skill | .cursor/skills/document-council/SKILL.md |
| Document council personas | standards/04-prompts/planning/document-council-personas.md |
| Linear status sync skill | .cursor/skills/linear-status-sync/SKILL.md |
| README update | .cursor/skills/README.md |