Skill Frontmatter

---
name: wrap-up
description: End-of-session ritual that audits changes, runs quality checks, captures learnings, and produces a session summary. Use when saying "wrap up", "done for the day", "finish coding", or ending a coding session.
user-invocable: true
allowed-tools: ["Read", "Bash"]
---

# Wrap-Up Ritual

End your coding session with intention.

## Workflow

1. **Changes Audit** — What files were modified? Anything uncommitted? TODOs left in code?
2. **Quality Check** — Run lint, typecheck, and tests. All passing? Any warnings?
3. **Learning Capture** — What mistakes were made? What patterns worked well? Format as `[LEARN] Category: Rule`
4. **Next Session Context** — What's the next logical task? Any blockers? Context to preserve?
5. **Summary** — One paragraph: what was accomplished, current state, what's next.

## Commands

\`\`\`bash
git status
git diff --stat

npm run lint 2>&1 | head -20
npm run typecheck 2>&1 | head -20
npm test -- --changed --passWithNoTests
\`\`\`

## Output

- Modified file list with uncommitted changes highlighted
- Quality gate results
- Captured learnings (if any)
- One-paragraph session summary
- Next session resume context

After completing checklist, ask: "Ready to end session?"

---
name: orchestrate
description: Wire Commands, Agents, and Skills together for complex features. Use when building features that need research, planning, and implementation phases.
user-invocable: true
agent: orchestrator
---

# Orchestrate - Multi-Phase Feature Development

Delegate to orchestrator agent for structured feature development.

## The Pattern

\`\`\`text
/develop <feature>
  │
  ├── Phase 1: Research (orchestrator agent)
  │   └── Score confidence → GO/HOLD
  │
  ├── Phase 2: Plan (orchestrator agent)
  │   └── Present plan → wait for approval
  │
  ├── Phase 3: Implement (orchestrator agent)
  │   └── Execute plan → quality gates
  │
  └── Phase 4: Review (reviewer agent)
      └── Code review → commit
\`\`\`

## Usage

When asked to build a feature:

1. **Start with research**: Delegate to orchestrator agent
2. **Wait for GO/HOLD**: Don't proceed if confidence < 70
3. **Present a plan**: List all files, approach, risks
4. **Get approval**: Never implement without explicit "proceed"
5. **Implement step by step**: Quality gates every 5 edits
6. **Review before commit**: Run reviewer agent

---
name: replay-learnings
description: Surface relevant past learnings for the current task
user-invocable: true
context: fork
allowed-tools: ["Bash"]
---

# Replay Learnings

Surface relevant learnings without polluting main context.

## Workflow

1. Ask user what they're working on
2. Search learnings database for relevant patterns
3. Present top 5 matches
4. Ask if user wants to apply any

## Search

\`\`\`bash
node -e "
const { createStore, searchLearnings } = require('pro-workflow');
const store = createStore();
const results = searchLearnings(store.db, process.argv[1], { limit: 5 });

if (results.length > 0) {
  console.log('Relevant learnings:');
  for (const r of results) {
    console.log('\\n#' + r.id + ' [' + r.category + '] ' + r.rule);
    if (r.mistake) console.log('  Mistake: ' + r.mistake);
    if (r.correction) console.log('  Correction: ' + r.correction);
    console.log('  Applied: ' + r.times_applied + 'x');
  }
}

store.close();
" "<query>"
\`\`\`