Testing & Debugging Skills

Invoke this skill when the user asks how to INSTALL or SET UP the product-shaping plugin for the first time — adding skills to Claude Code, Cursor, GitHub Copilot, Codex CLI, or another AI tool. Covers first-time installation, updating skills, verifying the setup, and configuring for the user's specific tool. Excludes: daily usage questions (use shape-cli-guide instead), writing product artifacts, and general programming help.

Challenge framing assumptions about WHAT to build before planning HOW.

Review implementation against plan for drift, dangerous decisions, and pattern…

Generate context/foundation/prd.md from shape-notes.md (or raw notes) against the locked PRD schema.

Generate context/foundation/roadmap.md from a PRD as an ordered set of vertical, end-to-end slices.

Drive an approved implementation plan to completion phase by phase, test-first, through the red→green→refactor cycle, but only for phases whose implementation does not exist yet. Reads a plan from context/changes/ /plan.md and the canonical Progress section, and for each phase first checks whether the phase is TDD'able and still unimplemented — if it is, you write a failing test (RED), make it pass with the minimal code (GREEN), then clean up (REFACTOR); if it is not TDD'able, you redirect that phase to /shape-implement; if implementation is already present, you stop and explain that TDD does not work for already existing code, then suggest /shape-implement for that phase. Mirrors /shape-implement (same plan, same Progress source of truth, same phase-end commit ritual and clipboard handoffs) but flips the order so the failing test always comes before the code. Assumes test infrastructure is already in place — it does NOT set up runners, configs, fixtures, or CI. Use this skill when the user says "tdd", "test-first", "red green refactor", "implement this plan test-first", "drive the plan with tests", or wants to execute an existing plan through a TDD loop. For plans where test-first does not fit, hand the phase to /shape-implement. For phases where the implementation already exists, stop instead of writing retroactive tests.

Stateful, phased test-rollout orchestrator for existing products. Writes a durable phased rollout document at context/foundation/test-plan.md BEFORE handing off, then drives each rollout phase into /shape-new → /shape-research → /shape-plan → /shape-implement. Re-running the skill re-derives state from which artifacts exist and resumes from the next pending rollout phase. Once a rollout change is opened, follow the established research → plan → implement process: after each major phase, suggest the next natural command unless there is a clear blocker. Use when the user says "create test plan", "plan tests", "test strategy", "phased test rollout", "continue test rollout", "risk map for testing", "QA spec", "AI-native testing strategy", "stwórz plan testów", "strategia jakości". Use AFTER /shape-prd and /shape-roadmap. Brownfield only; greenfield needs a PRD first.