Think through what you are about to build like a senior engineer before writing any code. Surfaces decisions, aligns on language, and produces a clear implementation plan you confirm before anything starts.
A planning skill that has the agent act as a senior engineer sitting with a developer to think through what is about to be built before any code is written. It frames the exchange as a collaborative thinking session rather than an interrogation, aiming to ensure both sides are building the same thing in their heads, to catch things that seem obvious but are not, and to align on approach before coding starts. The output is a clear implementation plan the developer confirms up front.
The method proceeds in ordered steps. First, it takes stock of what already exists by reading the feature description, context files, documentation, and existing code, and deliberately avoids asking about anything the docs already answer. Next, it aligns on language by identifying three to five ambiguous terms and proposing a definition for each for confirmation, updating immediately when corrected and not continuing until the vocabulary is shared. Then it thinks through the decisions that would meaningfully change what gets built, one question at a time, always sharing its own recommendation and reasoning so the developer has something to react to, skipping decisions rendered irrelevant by earlier answers, and working in order of downstream impact. It stops when every decision that would change the implementation is resolved, rather than exhausting every possible question, signaling completion by saying Blueprint ready.
After that signal, it produces an implementation plan with sections for what is being built, the agreed-on language, the decisions made and their reasoning, assumptions that were not explicitly confirmed, and a concise ordered list of how to build it. The plan is presented for explicit confirmation, and only then does implementation begin. The skill is explicit about what it is not: not an interrogation meant to catch the developer out, not a full specification document, and not an open-ended questioning loop. It is best used before starting a feature, when decisions and shared understanding need to be settled so building can start with confidence.
Not on its own. It runs a thinking session and produces an implementation plan; only after the developer explicitly confirms the plan does implementation begin.
To make sure both sides mean the same thing, it identifies three to five ambiguous terms, proposes a definition for each, and does not continue until the language is aligned, updating immediately if corrected.
It surfaces only the decisions that would meaningfully change what gets built, asks one at a time in order of downstream impact, and skips any decision made irrelevant by an earlier answer.
It stops when every decision that would change the implementation is resolved, then says Blueprint ready and writes the implementation plan for confirmation.
It includes what is being built, the agreed-on language, the decisions made with reasoning, any unconfirmed assumptions, and a concise ordered list of implementation steps.
Quick Setup:
.claude/skills/Repository
javascript-mastery-pro/skills