How to use the Stitch SITE.md Planner agent skill

What is an agent skill, and what does site-md do?

An agent skill is a folder containing a SKILL.md file of written instructions that an AI agent reads when a task matches the skill's description. The site-md skill has no scripts. It is a set of instructions that tells the agent how to turn a brief into a project constitution.

The agent acts as a Lead Product Owner and Architect. It writes a file named .stitch/SITE.md at the root of your project. According to the skill, that file works as long-term memory so coding agents stay aligned on scope, visual vibe and navigation across successive build iterations.

• Core Identity: project name, Stitch Project ID (a placeholder or the active ID), mission, target audience and voice.
• Visual Language: a primary, secondary and tertiary aesthetic keyword.
• Architecture & File Structure: a default root of site/public/, the asset flow from queue/ to site/public/, and a navigation strategy.
• Live Sitemap: pages marked [x] when complete and [ ] when pending, with at least index.html at initialization.
• Roadmap Backlog: tasks grouped as High, Medium and Low priority.
• Creative Freedom Guidelines.

Install the site-md skill

Download the ZIP for this skill from this page. Unzip it into one of two locations, depending on how you want to use it.

For a personal setup available across projects, unzip it into ~/.claude/skills/. For a single project, unzip it into that project's .claude/skills/ folder so it applies only there.

In the Claude apps, you can instead upload the skill under Settings → Capabilities → Skills.

• Personal: ~/.claude/skills/
• Single project: .claude/skills/ inside the project folder
• Claude apps: Settings → Capabilities → Skills, then upload

How to trigger the skill with a natural request

You do not need a special command. Describe what you want in plain language that mentions a project brief or requirements and asks for a SITE.md file. The agent should match the request to the skill's description, which covers analyzing project descriptions or site requirements and synthesizing SITE.md for the Stitch Build Loop.

Point the agent at your brief. The skill's first action is to locate and read the project description document or the text you provide.

• "Read docs/brief.md and create the .stitch/SITE.md planning file for this site."
• "Turn these requirements into a SITE.md with a prioritized backlog."
• "Use the site-md skill to draft the project constitution from this client brief."

What you need before you start

The skill expects a project requirements brief or description document. A Stitch Project ID is optional; if you do not have one, the skill uses the placeholder [Stitch Project ID].

The output is designed for the Stitch Build Loop. The agent needs Read and Write file access to read your brief and write .stitch/SITE.md. The skill lists a web_fetch tool in its allowed tools, but its instructions do not explicitly require fetching a URL, so you should not rely on it fetching pages for you.

• A requirements brief or project description
• Optional: an existing Stitch Project ID
• Read and Write file access for the agent
• Stitch Build Loop project context

Safety notes: scripts, network and sensitive content

This skill runs no scripts and uses no network access, according to its listing. It only reads your input and writes a Markdown file.

The written SITE.md is a file the agent can read and share in later iterations. If your brief contains confidential or sensitive details, remove them before you run the skill, or keep them out of the project folder.

• Runs scripts: no
• Uses network: no
• Anything in the brief can end up in .stitch/SITE.md, which later agent sessions can read

Check and refine the output

The skill's final step asks the agent to verify that all seven sections of the SITE.md template are present and properly formatted. Read the file yourself before building, because the agent may still misread a brief.

Keep the file current. The sitemap uses [x] and [ ] markers, so update them as pages are finished.

• Confirm the project name, mission and audience match your brief.
• Check that the sitemap lists the pages from your brief.
• Re-prioritize the backlog if the High, Medium and Low grouping does not match your goals.