ateam-discovery

Conducts a question-driven discovery phase producing JTBD sets, ADRs, decision records, and plans.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Product discovery often starts from fuzzy prompts or raw client transcripts with no structured way to turn them into validated jobs-to-be-done, architecture decisions, and research plans. This Skill runs a disciplined, human-in-the-loop discovery phase that converts raw input into durable product artifacts without inventing facts. ## Core Features & Use Cases - Ten-movement discovery workflow: Sequences challenge, run brief, research ingestion, straw-man JTBD drafting, dev review subagent, architecture drafting, ledger-driven grill, consolidated read-back, independence handoff, and a final write step. - Evidence discipline: Stages every source as an input batch with coverage rows, requires line citations for domain claims, tracks conflicts as ledger items, and binds decision records to falsifiable assumption records. - Human-gated decisions: Escalates blocking questions one at a time with recommended answers, never guesses demand-side answers, and serializes unanswered questions under an Awaiting answers section when no human responds. - Use Case: A product manager pastes a client interview transcript and asks the agent to run discovery; the Skill digests the transcript, drafts jobs and decision candidates, grills the human on blocking unknowns, and writes context.md, jtbd/ files, ADRs, decision records, ateam-plan.md, and research-plan.md. ## Quick Start Run the ateam-discovery skill on this client transcript to seed docs/product/ with jobs, decisions, and plans before any feature exists.

Frequently Asked Questions about ateam-discovery

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

FAQPage Schema
How do I run product discovery from a raw client transcript?▼

Invoke the discovery phase with the transcript as input; the Skill stages it as an input batch, digests it into a drafted context.md, and grills you one question at a time on blocking unknowns. It then writes jobs, decision records, ADRs, and plans after a consolidated read-back.

What artifacts does a discovery phase produce?▼

It writes context.md with sources and coverage, jtbd/ job files, adr/ architecture decision records, decisions/ product-scope records, ateam-plan.md, research-plan.md, and a staged grill digest. With a manifest present it also records gate_policy and run_brief.

Can the discovery skill run without a human present?▼

No. It is a grill that cannot run autonomously; if nobody answers it serializes blocking questions under an Awaiting answers section, commits, and halts. Answering its own demand-side questions is explicitly forbidden as autonomous degrade.

How does the skill handle conflicting input sources?▼

Conflicts become [conflict] ledger entries with both citations and what they block, never silent judgements. They route through the grill one at a time; unresolved conflicts stay open with TBD markers and a research-plan.md open question.

When should I reopen discovery versus use feature refinement?▼

Reopen discovery only when a change introduces a new job, audience, or load-bearing assumption; the Skill detects this iteration entry itself and classifies existing jobs as kept, reshaped, or superseded. Bounded changes to an existing product use the /feature refinement route instead.