Project Management

Project Planner

Turns a loose client brief into routes, features, content needs, dependencies, risks and acceptance checks.

What it does

Turns a loose client brief into routes, features, content needs, dependencies, risks and acceptance checks.

When to use it

Use before writing any code: new sites, redesigns, or a feature that doesn't yet have a verified delivery structure.

Problems it prevents

Prevents the common failure of starting to build before anyone has agreed what 'done' actually means.

Typical workflow

  1. Capture business and user goals
  2. Separate essential features from optional ones
  3. Map routes and dependencies
  4. Write acceptance checks per milestone

Example output

A structured plan: page list, must-have vs nice-to-have features, and a checklist each milestone has to pass before moving on.

What's included

  1. 01
    The complete prompt

    The full manual as a ready-to-save SKILL.md file, matched exactly to what ships in the T7 library.

  2. 02
    Install walkthrough

    Personal (~/.claude/skills/) and project (.claude/skills/) folder instructions, whichever fits how you work.

  3. 03
    Use notes

    How Claude invokes it, what a good result looks like, and what to check before you trust the output.

Installation

Save the manual as SKILL.md in ~/.claude/skills/project-planner/ to use it on every project, or in .claude/skills/project-planner/ to scope it to one repository. Then invoke it directly:

/project-planner

Read the official Claude Code skills guide

Works well with