Pocock Skills

Extract deep domain knowledge through structured interviewing. Build CONTEXT.md glossaries, write minimal ADRs, cross-reference code, and stress-test language with concrete scenarios.

Six-phase systematic debugging methodology. Build a feedback loop, reproduce the bug, form ranked hypotheses, instrument with tagged logs, fix at the correct seam, then post-mortem.

Systematic codebase improvement via full glossary, deletion test, HTML exploration reports, parallel interface design with competing constraints, and seam-based testing strategy.

Two-branch prototype strategy. Logic branch for state machines and reducers with TUI runners. UI branch with radically different variants and URL-param switching. Always throwaway.

Synthesize a complete PRD from context without an interview. Sketch test seams first, write full user stories, define implementation decisions without file paths, scope explicitly.

Convert a PRD into a dependency-ordered issue set using vertical slices. Classify AFK vs HITL. Write agent briefs that are behavioral not procedural, with complete acceptance criteria.

Produce clean handoff documents that reference artifacts by path, redact sensitive info, suggest relevant skills, and include argument hints for tailoring to different contexts.