Results for “peter-cook”

Synthesize source-indexed proof-material items into the final proof-usage playbook. Use when Codex needs to cluster proof items by proof shape, de-duplicate across sources, design reusable taxonomy entries, update proof-usage indexes and source maps, or preserve material-ID links from cooked proof entries.

Audits code quality against a shared contract, producing structured findings and blocking pipeline phases on critical issues without modifying code.

Implements a feature phase by phase from a phased JSON or Markdown plan, with configurable unit-test and quality-gate choices per phase, token-budgeted execution, resumable state, and TDD handoff.

Implements code features phase by phase from a JSON or Markdown plan, with configurable unit-test and quality-gate choices, token-budgeted execution, and resumable state.

A relentless interview to sharpen a plan or design.

Guides Directors and senior product leaders through the transition to VP or CPO with adaptive coaching across preparing, interviewing, landing, and recalibrating.

Interviews users relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree.

Runs a relentless interview that sharpens a plan or design. Use when the user wants to be grilled on an idea, pressure-test a plan, or refine a design through questioning.

Use the pk-doctor skill to run the aggregator health check and resolve

Police the project's vocabulary — bust vague terms, keep the CONTEXT.md glossary sharp, and lock in decisions worth remembering as ADRs. Use when the user debates naming, says "what should we call this", asks to pin down terminology, wants a decision recorded, or when another skill (hot-seat, whiteboard) surfaces a decision that clears the ADR bar. Just reading the glossary for vocabulary is NOT this skill — trigger only when the words or decisions are being changed.

Runs a relentless interview that sharpens a plan or design and creates docs (ADRs and glossary) along the way. Use when the user wants to stress-test a plan or design, or produce decision records.

Bitcoin Core JSON-RPC interface: authentication (cookie, rpcauth), wallet vs node RPCs, common verbs (getblockchaininfo, getrawtransaction, scantxoutset, importdescriptors, walletprocesspsbt, submitpackage, testmempoolaccept), error handling. USE WHEN: scripting bitcoind, integrating a service, debugging RPC errors.

Stress-test a plan or design by interviewing the user relentlessly about every aspect until reaching a shared understanding.

Runs and writes tests for a project, supporting unit, integration, and end-to-end scopes, plus two-pass TDD orchestration with quality-gate checks and regression sweeps.

Runs and writes tests, verifies behavior, and orchestrates two-pass TDD across scoped modes, blocking on quality gates and never editing production code.

Grill the user relentlessly about a plan, decision, or idea — one question at a time — until shared understanding is reached. Use when the user says "grill me", "stress-test this plan", "interview me about this", "poke holes in this", "challenge my thinking", or before committing to a non-trivial design.

Runs a structured interview session to sharpen a plan or design through relentless questioning.

PUA Loop — guided iterative development with recurring checks, completion evidence, and pause/abort markers. Use only when the user explicitly asks for loop/自动迭代 mode.

Socratic coach for breaking down problems to fundamental truths. Use when users want to think through a problem deeply, challenge assumptions, or find innovative solutions. Triggers on requests like "help me think through this", "let's break this down", "what are my blind spots", "I'm stuck on a problem", "challenge my assumptions", or explicit requests for first-principles thinking.

PUA Loop — guided iterative development with recurring checks, completion evidence, and pause/abort markers. Use only when the user explicitly asks for loop/自动迭代 mode.

Prepare GPT-pro-ready proof planning or diagnosis bundles from a user's idea, packaging claims, sources, givens, and open questions for review without solving gaps locally.

Put the user in the hot seat — one question at a time until their plan, decision, or idea actually holds up. Use whenever the user says "hot seat me", "grill me", "stress-test this", "poke holes in this", "am I missing anything", or drops a plan and wants it challenged before anyone acts on it — even if they never say the words. Also used as a sub-procedure by the whiteboard and connotation-cop skills.