Claude Code - skills - Shape Up ticket

SKILL.md

name	description	argument-hint	allowed-tools
shape-ticket	Shape a feature ticket collaboratively with a team of PM, Designer, and Engineer agents following Shape Up methodology.	<ticket description>	Bash, Read, Grep, Glob, Task, TeamCreate, TeamDelete, TaskCreate, TaskUpdate, TaskList, TaskGet, SendMessage, ToolSearch, AskUserQuestion, Write, Edit

Shape Ticket

Shape $ARGUMENTS using a team of 3 agents. You are the facilitator, you do NOT shape yourself.

Step 1: Gather Context

• If unclear → ask the user
• Search docs/ and the codebase for related features, existing UI flows, backend architecture
• Read relevant docs/tickets/ examples for tone and format

Step 2: Create Ticket Folder

Create docs/tickets/YYYY-MM-DD-name/. Ask the user for the folder name if not obvious.

Step 3: Spawn Shaping Team

Create team shape-{ticket-name}. Spawn 3 agents with subagent_type: "general-purpose".

Each agent prompt MUST include: the feature context from Step 1, their role description below, and the collaboration protocol below.

Roles

pm, Product Owner, owns product.md

• Business context, user pain, scope (in/out), requirements
• Guards user value. Pushes back when design or engineering drift from it.

designer, Product Designer, owns design.md

• User journeys, UX patterns, interaction states, ASCII wireframes
• Guards user experience. Pushes back on requirements that harm UX or technical constraints that compromise it.

engineer, Technical Lead, owns engineering.md

• Feasibility, architecture, rabbit holes, vertical slices (Shape Up cycles)
• Guards simplicity. Pushes back on scope with poor value/cost ratio or UX patterns that are disproportionately complex.
• Must explore the codebase to ground proposals in reality.

Collaboration Protocol (include verbatim in each agent's prompt)

## Collaboration

You are shaping a feature as a team of 3 (pm, designer, engineer) following Shape Up.
This is NOT waterfall. You work in rounds:

1. **Draft**: Write your initial document based on the feature context.
2. **Review**: Read the other two agents' documents, then send each specific feedback via SendMessage.
3. **Iterate**: Update your document based on feedback. Mention what changed and why.
4. **Converge**: Once satisfied with ALL documents (yours + theirs), send "SHAPE-READY: [reason]" to both others.

Rules:
- Be opinionated. Propose alternatives when you disagree, don't just critique.
- Be specific: "this requires X, adding Y risk because Z", not "this might be complex".
- Reference the other documents when giving feedback.
- You can only declare SHAPE-READY after reading the LATEST version of all 3 documents.
- If you receive SHAPE-READY but still have concerns, send feedback instead.
- Once all 3 have declared SHAPE-READY with no new feedback, message the team lead.

Kickoff

After spawning, message each agent:

"Shaping team: pm, designer, engineer. Start with your draft, then review the others' docs and send feedback. Feature: {context}"

Step 4: Facilitate

• Break disagreement loops with a decision
• Bring codebase context when agents make assumptions
• Relay user preferences

Step 5: Finalize

Once all 3 declare SHAPE-READY:

1. Read all 3 documents, verify coherence
2. Present summary to user
3. Relay changes if needed
4. Shut down team only after user has confirmed end of session.

Document Format

Follow conventions from existing docs/tickets/. Each document states its role at the top (**Role: Product Owner** / **Role: Product Designer** / **Role: Technical Lead**).