#PRD Intake

On-demand reference for ingesting a PRD, decomposing it into work items, and managing updates.

#Triggers

#Intake Flow

1. Detect source: File path, pasted text, or URL. Store a reference in .squad/team.md under ## PRD Source.
2. Store PRD reference: ```markdown ## PRD Source

Path: {path-or-inline} Ingested: {ISO date} Hash: {sha256 of content, for change detection} ``` 3. Spawn Lead (sync, premium bump) with decomposition prompt (see below). 4. Present work items to user for approval in table format. 5. On approval: Route items to agents respecting dependency order.

#Lead Decomposition Spawn Template

You are the Lead, decomposing a PRD into actionable work items.

PRD CONTENT:
{full PRD text}

TEAM ROSTER:
{roster from team.md}

TASK: Break this PRD into discrete, implementable work items. For each item provide:
- Title (imperative mood, concise)
- Description (acceptance criteria, technical notes)
- Estimated complexity: S / M / L
- Dependencies (list other item titles this blocks on)
- Suggested assignee (agent name from roster, based on expertise match)

OUTPUT FORMAT:
Return a markdown table:

| # | Title | Complexity | Dependencies | Assignee | Status |
|---|-------|-----------|--------------|----------|--------|
| 1 | {title} | {S/M/L} | — | {agent} | pending |

RULES:
- Items must be independently implementable (no item requires partial completion of another).
- Maximum 1 day of work per item (split larger items).
- Respect team expertise — don't assign frontend work to a backend specialist.
- Order by dependency graph (items with no deps first).
- Flag any ambiguities or missing information as "⚠️ Needs clarification: {question}".

#Work Item Presentation Format

Present to user as:

📋 PRD decomposed into {N} work items:

| # | Title | Size | Depends on | Assignee |
|---|-------|------|-----------|----------|
| 1 | ... | S | — | {Agent} |
| 2 | ... | M | #1 | {Agent} |

Ready to proceed? I'll route items respecting the dependency order.
⚠️ Clarifications needed: {list any flagged items}

#Mid-Project Updates

When the user says the PRD changed:

1. Re-read the PRD content.
2. Compute diff against stored hash.
3. Spawn Lead (sync) with a delta-decomposition prompt:
   • Show only NEW or CHANGED sections.
   • Ask Lead to identify: new items, modified items, obsoleted items.
4. Present changes to user: ``` 📋 PRD update detected: - New items: {count} - Modified: {count} - Obsoleted: {count} (will be cancelled if approved)

{table of changes}

Approve these updates? ``` 5. On approval: Cancel obsoleted work (if not yet started), update items, re-route.

#State Tracking

Active PRD state lives in team.md: - ## PRD Source section (path, date, hash) - Work items tracked as issues (GitHub) or in .squad/backlog.md (offline mode) - Completion percentage displayed in status checks