prd-council
Skill2 starsChanged 4 months agoNo licenceView on GitHub
Turn a feature idea into an execution-ready document set through an adversarial PRD "council": grill the user for requirements, draft a PRD, then debate it with OpenAI Codex round-by-round until BOTH sides approve, and finally emit a Technical PRD (one overall summary + one per UseCase) plus a task list with agent assignments, dependencies, and acceptance criteria — designed so a PdM-role agent could later distribute the work to specialist agents. Document-generation only (no agent execution). Writes local files under docs/prd/<slug>/; never publishes to external trackers. Uses codex-server (the user's ChatGPT subscription) for the debate loop. Use when the user wants a PRD reviewed/approved by Codex, a "PRD council", a Technical PRD for task distribution, or a task breakdown from a PRD. Trigger patterns (match any variation): prd-council / prd council / PRD council / PRD + {Codex, GPT, ChatGPT} + {議論, 相互承認, レビュー, 承認, debate, review, approve} / CodexとPRDを議論 / CodexとPRDを相互承認 / PRDをCodexと詰める / technical prd / technical product requirement document / 全体サマリー + UseCase + PRD / ユースケース別PRD / タスク振り分けドキュメント / PdM agent task distribution doc / PRDからタスクリスト / break a PRD into tasks / task breakdown from PRD / /prd-council
In this repository58 other files it gives its agents.
- AGENTS.mdAGENTS.md
- adversarial-panelSkill
- agents-initSkill
- agent-swarmSkill
- chrome-useSkill
- codex-cliSkill
- codex-serverSkill
- confluenceSkill
- deepenSkill
- dev-workflowSkill
- diagnoseSkill
- dotnet-seniorSkill
- e2e-testSkill
- en-to-ja-explainerSkill
- figma-shot-boardSkill
- gdrive-cliSkill
- grill-meSkill
- grill-to-implSkill
- grill-with-docsSkill
- handoffSkill
- improve-codebase-architectureSkill
- japanese-tech-writingSkill
- jira-cliSkill
- local-skill-factorySkill
- logo-imageSkill
- my-gdriveSkill
- my-skill-factorySkill
- naturalize-jaSkill
- natural-japaneseSkill
- notion-cliSkill
- openai-cliSkill
- orch-qaSkill
- parallel-investigateSkill
- playwright-cliSkill
- pm-reviewSkill
- postmortemSkill
- prototypeSkill
- pr-reviewSkill
- recap-to-notionSkill
- review-localSkill
- scenario-genSkill
- self-pr-reviewSkill
- session-handoverSkill
- session-recapSkill
- session-watchSkill
- skill-improveSkill
- slack-cliSkill
- slack-to-ticketSkill
- subagent-genSkill
- tddSkill
- test-scenarioSkill
- to-prdSkill
- triageSkill
- ui-spec-simSkill
- well-arch-costSkill
- well-arch-reliabilitySkill
- well-arch-securitySkill
- zoom-outSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
16 rules. About 0 are common, 6 are distinctive, and 10 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
10
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.