foomakers/pair — Prompts
Excerpt 1: pair-process-specify-prd — Phase 0 Idempotency Gate
Source: .claude/skills/pair-process-specify-prd/SKILL.md
## Phase 0: Detect Existing PRD (Idempotency Gate)
### Step 0.1: Check Current State
1. **Check**: Does [adoption/product/PRD.md](../../../.pair/adoption/product/PRD.md) exist?
2. **Act** (file exists): Read the file. Determine if it is a **template** (contains `[Product/feature name]` or `[Creation date]`) or a **populated** PRD.
- If **template**: treat as new PRD. Proceed to Phase 1.
- If **populated** and `$section` provided: jump to Phase 3 (selective update of that section).
- If **populated** and no `$section`: present current PRD summary and ask:
> PRD already exists for **[product name]**. Options:
> 1. **Update specific sections** — tell me which sections need changes
> 2. **Full review** — walk through the entire PRD for updates
> 3. **Cancel** — no changes needed
3. **Verify**: Mode is set to `create`, `update-section`, `full-review`, or `cancelled`. If cancelled → stop.
Technique: Idempotency gate with explicit state enumeration. The skill detects context before acting, exposing a choice menu rather than blindly overwriting.
Excerpt 2: pair-process-implement — Phase 0 BLOCKING Gate
Source: .claude/skills/pair-process-implement/SKILL.md
### Step 0.1: Load Story
1. **Check**: Is the user story already loaded in this session?
2. **Skip**: If yes, confirm story ID and move to Step 0.1b.
3. **Act**: Read the story from the PM tool (per [way-of-working.md](../../../.pair/adoption/tech/way-of-working.md)).
- Understand business value and acceptance criteria.
- Confirm epic context.
4. **Verify**: Story is fully loaded. If not → **HALT**.
### Step 0.1b: Activate Story in PM Tool (NEVER SKIP)
1. **Check**: Is the story already assigned to the current developer AND status is "In Progress"?
2. **Skip**: If BOTH conditions met, move to Step 0.2.
3. **Act**: Update the PM tool:
- **Assign** the story to the current developer (if not already assigned).
- **Set status to "In Progress"** in the PM tool board/project.
4. **Verify**: Story is assigned and In Progress. If PM tool is inaccessible → warn developer and continue.
Technique: Check-Skip-Act-Verify (CSAV) loop pattern with HALT escalation. Each step has a check for existing state (enabling idempotent re-runs), an optional skip (if already done), an action, and a verification gate.
Excerpt 3: pair-process-specify-prd — Section Checklist
Source: .claude/skills/pair-process-specify-prd/SKILL.md
### Step 1.2: Create Section Checklist
1. **Act**: Build a checklist of all PRD sections from the template:
```text
PRD CHECKLIST:
├── [ ] 1. Overview (name, version, date, owner, summary)
├── [ ] 2. Vision & Mission
├── [ ] 3. Problem Statement (current state, pain points)
├── [ ] 4. Goals & Success Metrics (KPIs with targets)
├── [ ] 5. Target Users (personas, journey)
├── [ ] 6. Solution Overview (core solution, features P0/P1/P2)
├── [ ] 7. User Stories & Acceptance Criteria (epics, stories, ACs)
├── [ ] 8. Technical Considerations (architecture, requirements, constraints)
├── [ ] 9. Design Requirements (UI/UX, visual)
├── [ ] 10. Timeline & Milestones (phases, dependencies)
├── [ ] 11. Risks & Mitigations (table)
├── [ ] 12. Launch & Go-to-Market (strategy, marketing, support)
└── [ ] 13. Post-Launch (monitoring, iteration plan)
**Technique**: Explicit checklist rendering before Q&A — the agent tracks coverage visually in the conversation so neither the agent nor user loses context of which PRD sections are still pending.