pbakaus_impeccable/skill/reference/shape.md

Shape

Plan the requested surface without writing implementation code. Resolve SKILL.md's init gate, then follow new-work.md through task discovery, grounded candidate derivation, external concept seeding when applicable, and the user's concept choice. Return here before the direction contract or build.

Write the brief

Turn the confirmed answers and selected concept into the smallest brief that can guide excellent implementation:

1. Surface job: who arrives, what they need to understand or do, and the visitor mode.
2. Selected concept: the product mechanism, structural thesis, narrative or task sequence, focal moment, and signature use inside DESIGN.md.
3. Scope: fidelity, breadth, interactivity, named target, and what must remain untouched.
4. Content and evidence: real copy, data, assets, states, ranges, and the proof the design must carry. Name missing inputs instead of inventing placeholders.
5. Interaction and layout: hierarchy, topology, responsive behavior, primary action, familiar affordances, and important state transitions. Describe intent, not CSS.
6. Implementation constraints: platform, framework, performance, accessibility, localization, and reusable project components.
7. Open decisions: only unresolved choices that would materially change the build.

Use a compact 3–5 bullet brief when the prompt, PRODUCT.md, DESIGN.md, and answers already settle the task. Use the full structure only for a genuinely ambiguous, multi-screen, or standalone planning request. Do not restate the conversation to look thorough.

Confirm and stop

In an attended run, present the brief through the structured question tool for explicit confirmation or one focused correction round. A simulated user counts. Then stop: shape never writes code or a direction contract.

When no human or structured answer mechanism exists, record the selected concept and material assumptions as the confirmation surrogate, return the brief, and stop.