pacific-context-challenge

Generate protocol-compliant adapter stubs for Bucket 3 operations requiring external services. Use when the user requests "adapter stub", "dry run", "Bucket 3", "Linear ticket stub", "Kafka stub", or needs a fail-soft fallback for unavailable services.

Refine rough ideas into validated design docs through collaborative dialogue. Use when the user says "brainstorm", "help me design", "explore a feature", "let's think about", or has a vague idea that needs structure before coding.

Add multi-layer validation to fix bugs caused by invalid data. Use when debugging data corruption, invalid input reaching deep execution, "defense in depth", or when a bug needs structural prevention at every layer.

Capture session context for seamless continuity. Use when the user says "handoff", "wrap up", "end session", "pass the baton", "save progress", or needs to preserve working state for the next session.

Adversarial code review that iterates to convergence. Use when the user says "hostile review", "adversarial review", "tear this apart", "find all issues", or needs a thorough skeptical review of code or design.

Convert analysis results or review findings into actionable implementation plans. Use when the user says "turn insights into a plan", "prioritize findings", "action items from review", or has unstructured observations that need to become executable tasks.

Classify PRs and produce a priority-ordered merge plan. Use when the user says "merge order", "which PR first", "merge plan", or has multiple PRs targeting the same branch that need sequencing.

Generate YAML ticket contract templates with deterministic repo detection. Use when the user says "create ticket", "ticket template", "plan ticket", "YAML contract", or needs a structured ticket from a plan or task description.

Take an open PR from draft to merge-ready through conflict resolution, review feedback, and quality passes. Use when the user says "polish PR", "fix PR", "make PR merge-ready", "address review comments", or has an open PR with issues.

Systematic PR review with severity classification and merge readiness verdict. Use when the user says "review PR", "check this PR", "is this merge-ready", or needs a structured assessment of pull request changes.

Find the root cause of bugs through structured hypothesis testing. Use when the user says "debug", "fix this bug", "why is this failing", "flaky test", "regression", or is dealing with a traceback or unclear failure.

Create isolated git worktrees with verified clean baselines. Use when the user says "worktree", "isolated branch", "work on multiple branches", or needs feature isolation without switching branches.

Convert design docs into step-by-step TDD implementation plans. Use when the user says "write a plan", "implementation plan", "TDD plan", "break this into tasks", or has a design doc that needs to become executable steps.