Pm Working Backwards Agent
Description
Multi-agent CrewAI pipeline that turns a product problem statement into a research brief, PRFAQ, BRD, and build spec. Tiered model routing (Opus/Sonnet/Haiku), inter-stage verification gates, replay-based regression testing, and LLM-as-judge quality evals. Built on Claude and AWS Bedrock.
Installation
This entry records only its repository, not the path inside it, so there is no
exact command to give. Open the source below and copy the folder into
~/.claude/skills/, or the file into ~/.claude/agents/.
README
Working Backwards Agent for Product Managers
An open-source multi-agent AI system that guides product managers from a rough problem statement through stakeholder-ready research, a Working Backwards PRFAQ, a design brief with screen inventory and user flows, a BRD, and an engineer-ready build spec. Built on [CrewAI](https://www.crewai.com/) and Claude.
This is for product managers, not engineers. If you can fill out a markdown template and copy-paste an API key, you can run it. See [SETUP.md](SETUP.md) for a step-by-step walkthrough that assumes you have never used a terminal.
How it works
flowchart LR
A[input brief
.md or .yaml] --> B[Agent 1
Research]
B --> C[research_brief.md]
C --> D[Agent 2
PRFAQ]
D --> E[prfaq_v1.0.md]
E --> K[Agent 3
Design Brief
optional]
K --> L[design_brief_v1.0.md]
L --> F[Agent 4
BRD + Build Spec]
E -. "--skip-design" .-> F
F --> G[brd_v1.0.md]
F --> I[build_spec.md]
I --> J[Drop into
Kiro / Claude Code / Cursor]
Four agents, five artifacts. Agent 3 (Design Brief) synthesizes the PRFAQ and research into a screen inventory, user flows, and design principles. It's optional in the full pipeline — pass `--skip-design` to reproduce the three-agent behavior. Agent 4 produces two artifacts in sequence — the BRD first, then the build spec after you approve the BRD. In the code, Agent 4 is two tasks within one agent, not two separate agents. SVG wireframe generation is coming soon; today Agent 3 produces the design brief only.
You write a short problem statement. The agents do the research, write the Working Backwards document, translate it into requirements, and produce a build spec your engineers (or coding agent) can run with. You stay in the loop at every handoff.
What This System Is Not
This system does not replace your existing tools:
- Not a replacement for Jira or Linear. It produces requirements, not
Related Skills
Spec Kit
💫 Toolkit to help you get started with Spec-Driven Development
Testing Webapp Testing
Test local web applications using Playwright for UI verification and debugging
Testing #29
, [#52](https://github.com/affaan-m/everything-claude-code/issues/52), [#103](https://github.com/affaan-m/ever
Testing Fix Issue
by metabase - Addresses GitHub issues by taking issue number as parameter, analyzing context, implementing sol
Testing Pypict Test Design
Design comprehensive test cases using PICT (Pairwise Independent Combinatorial Testing) for optimized test sui
Testing gstack
| 15,000+ | Garry Tan's exact Claude Code setup: 6 opinionated tools that serve as CEO, Eng Manager, Release M
Testing