start-issue
start-issue
Workflow
1. Get the issue ID
Ask the user for the Linear issue identifier if not already provided (e.g. ENG-42).
2. Fetch issue + parent PRD (parallel)
In a single message, use the Linear MCP tools to:
- Fetch the issue:
get_issue(id, includeRelations: true) - From the
relatedTofield, identify the parent PRD issue (the one that looks like a PRD — has a Problem Statement / User Stories structure, typically the issue that spawned this slice via/prd-to-issues). Fetch it withget_issue.
If no parent PRD exists, note it and continue.
3. Create the git branch
More from maxmurr/agents-skills
submit-pr
Submit implementation as a pull request. Runs tests, creates a PR with the Linear issue linked, and posts the PR URL as a comment on the Linear issue. Use when implementation is complete and user wants to open a PR, submit work, or create a pull request.
2index-knowledge
Generate hierarchical AGENTS.md + CLAUDE.md knowledge base for a codebase. Creates root + complexity-scored subdirectory documentation with both file types.
2tdd
Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.
1atdd
Outside-in TDD with double-loop (acceptance + unit). Use when user wants acceptance-test-driven development, outside-in TDD, London-school TDD, GOOS-style development, or wants to drive design from user-facing behavior inward.
1prd-to-issues
Break a PRD into independently-grabbable Linear issues using tracer-bullet vertical slices. Use when user wants to convert a PRD to issues, create implementation tickets, or break down a PRD into work items.
1write-a-prd
Create a PRD through user interview, codebase exploration, and module design, then submit as a Linear issue. Use when user wants to write a PRD, create a product requirements document, or plan a new feature.
1