Page Brief

Create OR review a page-brief — the artifact BETWEEN a wireflow and the full PRD. It turns each unique page/screen of a product into documented requirements TIED TO JOBS: a self-contained board card per page (what the page is accountable for, the job-tagged checklist of what it must let you do, the journeys it appears in, what it connects to, and the acceptance criteria that say how you'd know it's right). It is the "PRD per page", not a sitemap — and it stops ABOVE the screen: no components, no layout, no hierarchy. Use whenever the user wants to "spec the pages", "document each screen", turn a wireflow + live design into per-page requirements, or asks "what does this page need to do / which jobs pass through it" — even if they never say "page-brief". Natural NEXT STEP after the wireflow skill. ALSO use it to REVIEW an existing page-brief / screen catalog. In the A-Team pipeline this is a definition-phase skill: output lands in docs/features/<slug>/briefs/pages/, job codes are the durable [[NN]] ids from docs/product/jtbd/, and pipeline mode derives all cards with flags headlined at the gate while standalone runs the per-page grill. CREATE gates on JTBD quality first, then generates verified SVG/HTML cards (self-checked by rendering and Reading the output) and can rebuild in FigJam. Do NOT use for a full PRD (that consumes this), wireframes / UI design / component specs, a wireflow (use the wireflow skill), or a sitemap.

mkdir -p ~/.claude/skills/page-brief
curl -L https://claudskills.com/skills/page-brief/SKILL.md \
  -o ~/.claude/skills/page-brief/SKILL.md

@misc{page-brief-2026,
  author    = {subvisual},
  title     = {Page Brief [Claude Code skill]},
  year      = {2026},
  publisher = {ClaudSkills},
  url       = {https://claudskills.com/skills/page-brief/}
}