plan-site

Generates five planning artifacts from a validated site brief.

Updated Apr 20, 2026
One-click install
npx skills add https://github.com/calebaero/website-factory --skill plan-site-calebaero
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-site
Source: https://github.com/calebaero/website-factory/tree/main/skills/plan-site
Command: npx skills add https://github.com/calebaero/website-factory --skill plan-site-calebaero

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turn a validated site brief into a complete planning bundle without scaffolding, producing five artifacts the downstream phases will read.

Core Features & Use Cases

  • Validate briefs (wf-validate-brief) and ensure contract cleanliness.
  • Select production archetype (wf-select-archetype) and seed the planning artifacts.
  • Compose site-plan.json, site-map.md, content-model.json, design-tokens.json, and implementation-backlog.md using reference skills under skills/*.
  • Surface refusals and open questions the user must resolve before build.

Quick Start

Run /website-factory:plan-site <path-to-site-brief.json> to generate the five planning artifacts.

Frequently Asked Questions about plan-site

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn a validated site brief into a complete planning bundle?

A site planning bundle requires five specific artifacts: site-plan.json, site-map.md, content-model.json, design-tokens.json, and implementation-backlog.md. These files configure downstream build phases without needing immediate scaffolding.

How do I generate design tokens and a site map from a project brief?

Generating design tokens and a site map from a project brief involves validating the brief, selecting a production archetype, and composing the artifacts using reference skills. This creates the design-tokens.json and site-map.md files for your site.

Do I need a validated brief before generating a site plan?

Yes, you need a validated brief before generating a site plan. The process runs a validation workflow to ensure contract cleanliness and surfaces refusals alongside open questions that you must resolve before proceeding to the build phase.

What are the limitations of automated site planning from a brief?

A key limitation of automated site planning is that it surfaces refusals and open questions you must manually resolve before the build phase begins. It also relies on selecting a predefined production archetype rather than generating entirely custom architectural patterns.

Can I use a site plan to create an implementation backlog for my build?

Yes, you can use a site plan to create an implementation backlog. The planning process directly outputs an implementation-backlog.md file, which translates the validated brief and selected archetype into actionable build tasks.