review-product-questions
Skill2 starsChanged 4 months agoMITView on GitHub
Phase 1 engg-reviews (PE, optional): interactively walk product questions from a PRD-Codebase-Map. Lets a product-minded PE refine recommendations (scenario, stance, alternatives) before posting to the Meta PR. Writes PE-Product-Stance artifact — proposals only, not PM authority. Does not edit the PRD, does not set gate labels. Skip and go straight to /post-product-questions if PE does not want this pass.
In this repository22 other files it gives its agents.
- ground-specSkill
- initiative-feasibilitySkill
- learning-extractSkill
- loop-specSkill
- pre-implementSkill
- purge-initiative-artifacts-appSkill
- spec-draftSkill
- spec-implementation-planSkill
- spec-technical-reviewSkill
- ensure-repo-graphSkill
- post-product-questionsSkill
- prd-codebase-mapSkill
- commit-workspaceSkill
- create-board-ticketsSkill
- open-draft-prSkill
- prd-impact-mapSkill
- prd-qualitySkill
- prd-thinkSkill
- purge-initiative-artifacts-metaSkill
- review-findingsSkill
- update-documentsSkill
- validate-requirementsSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 3 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 41
Read one map (or prior stance file) — do not re-run graphs.
- Distinctive: line 44
Prefer AskQuestion when available.
- Distinctive: line 48
Do not edit the PRD or outline.
- Very specific: line 50
After this skill, typical next step is /post-product-questions (uses stance file when present).
- Very specific: line 108
Use contract: engg-reviews/v1 and stage review-product-questions.
- Very specific: line 110
Always gate_coupled: false.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
Review product questions (PE stance — optional)
Interactive pass for a PE with product perspective: refine codebase-grounded
questions and PE recommendations before /post-product-questions.
Optional. Some PEs skip this and post the map as-is.
Not PM authority. Refined stances are still proposals for PM on the Meta PR.
Not /validate-requirements / /update-documents / PRD edits.
Question shape: ../references/product-question-template.md.
Handoff: ../references/handoff-adjunct.md.
When to use
| Use | Skip |
| PE wants to sharpen scenarios / pick a recommended stance | PE only wants to publish map questions |
| Senior PE owning product tradeoffs with eng evidence | Hand all product calls to PM untouched |
NON-NEGOTIABLE
- Read one map (or prior stance file) — do not re-run graphs.
- Present each question with scenario, example, recommendation, why, alternatives, evidence before asking how to refine.
- Prefer AskQuestion when available; otherwise chat options and wait.
- Record refined PE stance into
out/reports/PE-Product-Stance-{INIT}.md(or pe-workspace equivalent). - Label every decision as
pe_proposal— neverpm_approved. - Do not edit the PRD or outline.
gate_coupled: false. Noimpact-map-*/spec-*mutations.- After this skill, typical next step is
/post-product-questions(uses stance file when present).
Inputs
- Map path — (REQUIRED)
PRD-Codebase-Map-{INIT}.md - Mode — all / conflicts-only / PE-selected IDs
Process
Phase 1 — Setup
- Parse § Product questions (
PQ-*). - Summarize counts by delta.
- Entry gate AskQuestion:
- refine-all — Walk all questions interactively
- conflicts-only — Walk conflict/partial only
- skip — Skip; go to /post-product-questions with raw mapPhase 2 — Per question (PE refine)
For each selected question, show full template fields, then:
Map recommendation: …
Why: …
AskQuestion:
- keep-recommendation — Keep map recommendation as PE stance
- choose-alternative — Prefer alternative A/B (ask which; capture wording)
- custom-stance — PE provides different recommended product stance
- drop-question — Do not post this Q (record reason)
- needs-pm-only — Post Q but clear PE recommendation (PM must decide cold)Record: question id, pe_action, refined_recommendation, notes.
Phase 3 — Stance artifact
Write references/output-template.md.
Chat summary: kept / changed / dropped counts.
Phase 4 — Handoff
| Outcome | When | next_candidates |
pass | Stance file written | post-product-questions |
skipped | PE skipped entry gate | post-product-questions |
needs-input | Stopped mid-walk | review-product-questions |
Workflow handoff
Append the envelope from
../references/handoff-adjunct.md.
Use contract: engg-reviews/v1 and stage review-product-questions.
Always gate_coupled: false. Does not navigate sdd-delivery/v2.
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.

