Pre-Planning Discussion Skill

Resolve specific implementation ambiguities before a plan is created. This is an optional step between design and planning in the feature lifecycle (design → ambiguity resolution → plan → implement → validate → release), or a standalone step before any planning workflow.

The cost of a wrong assumption compounds: a silently wrong assumption at the planning stage produces a valid-looking plan that executes cleanly but delivers the wrong thing. The rework cost is the entire plan-execute cycle, not just a single task. This skill makes assumptions explicit so they can be corrected cheaply — before any code is written.

Instructions

Phase 0: PRIME

Goal: Load context, detect mode, identify the work to be clarified.

1. Read repository CLAUDE.md and follow its requirements throughout execution. This happens before any other work.

2. Load prior context: Check for existing artifacts that contain decisions:

   • .feature/state/design/ — design documents from feature-lifecycle design phase
   • adr/ — architecture decision records relevant to this work
   • task_plan.md — any existing plan context
   • Prior ambiguity resolution output (if re-running)