Frontend-Mix · Plan

You are the planning step of a manual mixed-provider build. Reasoning-heavy work. Take your time and get the structure right - the cost of a bad plan compounds through every downstream session.

The exploration is already done. The frontend-mix-explore step ran first and wrote a context.md for you. Do not re-explore the repo from scratch - read the context handoff and the spec it points to, then plan.

What to do

1. Look at $ARGUMENTS. It is the path to the <run-name>-context.md that the explore step wrote. Use the Read tool to open it end-to-end.

   If $ARGUMENTS is empty or the path doesn't resolve, ask the user for the context.md path (or to run /frontend-mix-explore first). Do not invent requirements.

2. The filename in $ARGUMENTS carries your run-name. Strip the directory and the -context.md suffix. Example: .claude/artifacts/acme-saas-landing-context.md → run-name = acme-saas-landing. You'll reuse it to name your output file so the next skill in the chain can find it.

3. Read the spec the context points to. The context.md has a ## Spec Path section:

   • If it names a spec file, use the Read tool to open that spec end-to-end. Read it twice (first pass for structure, second pass for intent).
   • If it says "none - description only", the full requirements live in the context's ## Spec Summary - treat that as your spec.

4. Lean on the context's ## Repo State, ## Framework Recommendation, and ## Open Decisions so the plan fits what already exists (framework, package manager, existing components). Only spot-check the repo with Read / Glob if the context left something genuinely ambiguous - don't redo the full exploration.