ateam-definition

Conducts PRD, epics, wireflow, and page-brief skills into one reviewed definition set.

Updated Jul 10, 2026
One-click install
npx skills add https://github.com/subvisual/the-a-team --skill ateam-definition-subvisual
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ateam-definition
Source: https://github.com/subvisual/the-a-team/tree/main/.claude/skills/ateam-definition
Command: npx skills add https://github.com/subvisual/the-a-team --skill ateam-definition-subvisual

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a product discovery North Star into a coherent, reviewable definition set requires coordinating PRD writing, epic bundling, wireflow rendering, and page briefs without inventing facts or losing traceability to jobs-to-be-done. ## Core Features & Use Cases - Orchestrated definition pipeline: Sequences the prd-writer, epics, wireflow, and page-brief craft skills into one definition set with requirement-level acceptance criteria traced to JTBD ids. - Draft + review honesty: Drafts with visible TBDs and open questions instead of interrogating or inventing answers, and reports blocking flags loudly for the gate review. - Rendered self-verification: Generates wireflow and page-brief boards, rasterizes them to PNG, and reads every render to iterate until clean before delivery. - Use Case: After discovery has produced docs/product/jtbd/ jobs, invoke this skill to produce prd.md, docs/product/epics/ entries, and briefs/wireflow plus briefs/pages boards, then complete the phase through the feature CLI with an honest blocking-flags report. ## Quick Start Ask the agent to run the definition phase for the current feature using the existing docs/product North Star and produce the PRD, epics, wireflow, and page briefs with a gate report.

Frequently Asked Questions about ateam-definition

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

FAQPage Schema
How do I run the definition phase for a feature in the A-Team harness?▼

Invoke the ateam-definition skill after discovery has produced active jobs in docs/product/jtbd/. The orchestrator calls feature-cli.mjs start first, then the skill drafts the PRD, epics, wireflow, and page briefs, and completes via feature-cli.mjs complete with the manifest revision.

What artifacts does the definition phase produce?▼

It produces prd.md with requirement-level acceptance criteria traced to job ids, docs/product/epics/ entries bundling every requirement, and briefs/wireflow plus briefs/pages directories containing board.json specs, rendered SVG/HTML, and PNG verification copies.

Can I run the definition skill standalone without a manifest?▼

Yes. When no feature manifest exists, the skill takes its prompt from invocation args, skips manifest writes, and the in-conversation review replaces the orchestrator gate. Standalone mode is never a weaker-review path.

What happens when required facts are missing during definition?▼

Missing facts become visible TBDs and open questions rather than invented answers, and are mirrored into research-plan.md. A TBD inside Must scope is reported as a blocking flag at the gate instead of being silently filled.

Why does the definition phase fail when docs/product/jtbd/ is empty?▼

The skill consumes jobs verbatim by id and never fabricates a North Star. If no active jobs exist, it leaves the phase status as in_progress and reports that discovery must run first.