buildable-planner

Buildable Planner Skill

Use this skill to classify prompts, choose an archetype, decide whether questions are needed, and produce a top-down phase plan plus app spec.

Inputs

• user prompt
• optional user-provided screenshots, documents, or source files
• optional existing repository context
• optional local preferences

Resolve all referenced paths from the Buildable plugin or repository root.

Reference Loading Contract

Mandatory order:

1. Run buildable plan "<prompt>" when available. Use --file <path>, --reference <path>, or --screenshot <path> for explicit user-provided files. It saves .buildable/phase-plan.md/json/toon by default; use --no-write only for terminal-only inspection.
2. Load only appSpec.references.
3. Inspect only explicit appSpec.referenceInputs supplied by the user.
4. Do not load all templates.
5. Do not load whole knowledge/ or templates/ directories.
6. Load starter source only for the selected template and only when generating or editing it.

Use knowledge/INDEX.md and templates/INDEX.md only for discovery when the CLI is unavailable.

Workflow

1. Prefer buildable plan "<prompt>" when the CLI is available.
2. Use core/archetype-registry.json tags for lightweight matching before opening archetype docs.
3. Apply core/ask-vs-build-policy.md.
4. Apply core/activation-policy.md.
5. Load the selected knowledge/archetypes/<archetype>.md.
6. Load matching files from knowledge/data-models/ and knowledge/screen-graphs/ when they exist.
7. Select the best templates/<target>/<archetype>/template-spec.json.
8. Select compact UI/UX direction from core/design-system-registry.json and include it as appSpec.designSystem.
9. Select compatible micro-blocks from blocks/registry.json and include them as appSpec.blocks; append only selected block references to appSpec.references.
10. Include appSpec.mockData with realistic local seed-data guidance and state coverage.
11. Include appSpec.referenceInputs when users attach screenshots/files; preserve paths and inspection instructions without pasting file contents into the prompt.
12. Include appSpec.promptRefinement with assumptions, optional sharpening questions, and default answers.
13. Include appSpec.planAudit with audit-first gates for scope, template status, references, mock data, UI/UX, local-first rules, auth/persistence, and review.
14. Produce an app spec using core/app-spec-schema.md.
15. Include a phase plan: clarify if needed, plan, mock data, design, build, review.
16. Include explicit non-goals to prevent hosted feature drift.
17. Ask questions with restraint:

• Ask blocking appSpec.questions first when questionsNeeded is true.
• When there are no blockers, ask at most one or two promptRefinement.optionalQuestions only if they would materially improve the result.
• If the user wants to proceed, use promptRefinement defaults instead of continuing to interrogate.

1. End with a short satisfaction checkpoint:

• If the user is not satisfied, ask them to stay in Buildable Planner and revise the saved plan with a prompt such as "Buildable Planner: keep this direction, but make the reminder features stronger."
• If the user is satisfied, suggest the correct next skill for the target: Buildable Web Builder for web or Buildable Mobile Builder for mobile. The builder must read the saved .buildable/phase-plan.json or .buildable/phase-plan.toon compact contract, then load only appSpec.references and the selected starter source.

1. When the user asks for login, auth, accounts, protected routes, or an explicit auth flag, include appSpec.auth and the auth references. Default to local/mock auth behind an auth seam; do not choose a hosted provider unless the user names one.