prd
/prd
Create agent-friendly Linear tickets with PRDs, sub-issues, and clear success criteria. Use when planning features or breaking down work for agentic coding.
- Author
- joa23 ↗
- Repository
- linear-cli ↗
- Licence
- MIT
- Last repository change
- 13.09.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 13.09.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Create agent-friendly Linear tickets with PRDs, sub-issues, and clear success criteria. Use when planning features or breaking down work for agentic coding.
Original author description
Create agent-friendly Linear tickets with PRDs, sub-issues, and clear success criteria. Use when planning features or breaking down work for agentic coding.
How it works
- When to Use
- Process
- Ticket Structure
- Example Commands
- Best Practices
SKILL.md preview
--- name: prd description: Create agent-friendly Linear tickets with PRDs, sub-issues, and clear success criteria. Use when planning features or breaking down work for agentic coding. --- # PRD Skill - Create Agent-Friendly Tickets You are an expert at breaking down features into well-structured, agent-friendly Linear tickets. ## When to Use Use this skill when: - Planning a new feature - Breaking down a large task into sub-issues - Creating tickets that AI agents will implement ## Process 1. **Understand the Request** - Ask clarifying questions if the scope is unclear - Identify the core problem being solved 2. **Create the Epic/Parent Issue** Use `linear issues create` with: - Clear, action-oriented title - Problem/Context section - Requirements (must-have vs nice-to-have) - Success criteria (testable, specific) 3. **Break Down into Sub-Issues** Each sub-issue should: - Be completable in one focused session (<150k tokens of context) - Have clear, verifiable success criteria - Include verification commands (tests to run) - Define boundaries (what's in/out of scope) 4. **Set Up Dependencies** Use `--depends-on` and `--blocked-by` to create proper dependency chains. ## Ticket Structure ```markdown ## Problem/Context [1-2 sentences explaining why this work is needed] ## Requirements ### Must Have - [ ] Requirement 1 - [ ] Requirement 2 ### Nice to Have - [ ] Optional feature ## Success Criteria - [ ] Specific, testable criterion 1 - [ ] Specific, testable criterion 2 ## Verification ```bash # Commands to verify the work is complete make test npm run lint ``` ## Boundaries ### In Scope - What this ticket covers ### Out of Scope - What should be separate tickets ``` ## Example Commands ```bash # Create parent issue linear issues create "User Authentication System" \ --team ENG \ --description "$(cat prd.md)" \ --priority 2 # Create sub-issue linear issues create "Implement OAuth2 login flow" \ --team ENG \ --parent ENG-100 \ --description "Implement OAuth2 with Google provider..." # Set dependencies linear issues update ENG-102 --blocked-by ENG-101 ``` ## Best Practices 1. **Size tickets appropriately** - Each should be 1-4 hours of focused work 2. **Include test commands** - Always specify how to verify completion 3. **Be explicit about scope** - Prevent scope creep with clear boundaries 4. **Use Labels** - Add `agent-ready` label for tickets ready for AI implementation
Files in this package (2)
- SKILL.md 2 KB
- template.md 1 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · joa23/linear-cli | 100 | MIT |
| stefanoskarakasis/product-marketing-skills | 100 | MIT |
| duronext/jig | 100 | MIT |
| OpenHands/extensions | 100 | MIT |
| alienfast/claude | 100 | MIT |
| rafagomes/ai-workflow | 100 | MIT |
| nkhanhpham99/ai-pm-os | 100 | MIT |
| jeffersonvalente/cardume | 100 | MIT |
| fakoli/anvil | 100 | MIT |
Database snapshot: 13.11.2026 · package version 74dc1912f972 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 95linear-issue-sync
Sync Linear issues with local tasks. Use during daily planning or when user asks about Linear issues. - 100writing-feature-prds
Use when starting a new feature, defining requirements before implementation, or when the user says "new feature", "create a spec", "create a PRD", or "feature PRD". - 100work-tracking
Structure work using parent-feature and child-work-item hierarchy compatible with Linear and GitHub. Use when planning features, breaking down work, creating issues, or organizing tasks. - 100ralph-prd
Generate a Product Requirements Document (PRD) for a new feature. Use when planning a feature, starting a new project, or when asked to create a PRD. Triggers on: create a ralph prd, write ralph prd for, plan this feature with ralph, ralph requirements for, ralph spec out. - 100create-prd
Create a product requirement document (PRD) for a new feature. Use when the user wants to create a new feature, plan a feature, or write a PRD. - 95prd-generator
Generates comprehensive Product Requirements Document from product plan. Creates PRD.md with features, user stories, acceptance criteria, and success metrics. Use when creating product requirements.