prd-from-context
Skill1 starsChanged 5 months agoMITView on GitHub
Turn existing conversation and repository context into a concise PRD without inventing new requirements. Use when enough product context exists but the work needs a durable product-shaped specification before planning. Conversation summary, user goals, constraints, non-goals, target users, acceptance criteria, and open questions. A PRD draft, assumptions list, acceptance criteria, and links to relevant context or ADRs. Inventing product requirements, over-specifying UI or architecture too early, or skipping user approval for high-impact scope. PRD separates facts from assumptions; acceptance criteria…
1 other project uses a version of this.
Adopted by
Most recently taken up by
- MADTeacher/skillstheir own version, first seen Nov 15, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- MADTeacher/skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository117 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- advanced-orchestrationSkill
- architect-agentSkill
- implementer-agentSkill
- quality-councilSkill
- reviewer-agentSkill
- tester-agentSkill
- writer-critic-pairSkill
- authoring-skillsSkill
- api-endpoint-qualitySkill
- async-job-qualitySkill
- auth-qualitySkill
- db-migration-qualitySkill
- frontend-state-qualitySkill
- acceptance-criteriaSkill
- adaptive-flowSkill
- adaptive-prompt-selectionSkill
- adversarial-code-reviewSkill
- architecture-decision-recordsSkill
- brainstormingSkill
- brownfield-spec-enhancementSkill
- bug-fix-lifecycleSkill
- checkpoint-validationSkill
- cicd-integrationSkill
- clarify-before-codeSkill
- claude-code-hooks-packSkill
- code-context-packSkill
- code-intelligence-reviewSkill
- context-policySkill
- context-rich-implementationSkill
- crash-proof-planningSkill
- critique-pass-protocolSkill
- dependency-aware-task-orderingSkill
- deprecation-migrationSkill
- disciplined-diagnosisSkill
- docs-authorSkill
- executing-plansSkill
- external-skillSkill
- finishing-a-development-branchSkill
- git-guardrailsSkill
- goal-driven-executionSkill
- grill-user-before-buildingSkill
- guard-bypass-protocolSkill
- improve-codebase-architectureSkill
- incremental-reviewSkill
- issue-slicingSkill
- lessons-learned-dbSkill
- loop-engineeringSkill
- model-aware-configSkill
- model-weakness-memorySkill
- multi-repo-learningSkill
- orchestration-workflowsSkill
- plan-driven-executionSkill
- plan-from-specSkill
- project-constitutionSkill
- prompt-architectureSkill
- prototype-before-commitmentSkill
- quality-engineSkill
- quality-execution-contractSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 20
Use when enough product context exists but the work needs a durable product-shaped specification before planning.
- Distinctive: line 32
Ask for approval before slicing or implementation when scope is meaningful.
≈ “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.
Files
Skill: PRD From Context
Purpose
Turn existing conversation and repository context into a concise PRD without inventing new requirements.
When to use
Use when enough product context exists but the work needs a durable product-shaped specification before planning.
Inputs
Conversation summary, user goals, constraints, non-goals, target users, acceptance criteria, and open questions.
Workflow
- Extract only stated or clearly implied requirements.
- Mark assumptions and open questions.
- Use
templates/prd-template.md. - Define user problem, outcomes, scope, non-goals, acceptance criteria, and verification.
- Ask for approval before slicing or implementation when scope is meaningful.
Outputs
A PRD draft, assumptions list, acceptance criteria, and links to relevant context or ADRs.
Failure modes
Inventing product requirements, over-specifying UI or architecture too early, or skipping user approval for high-impact scope.
Verification checklist
PRD separates facts from assumptions; acceptance criteria are testable; non-goals are explicit; approval path is clear.
Ghi chú tiếng Việt
Dùng để biến ngữ cảnh đã trao đổi thành PRD gọn. Không phỏng vấn lại nếu đủ thông tin; không bịa requirement. File liên quan: templates/prd-template.md, commands/vibe-to-prd.md.
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.