- name
SKILL.md
स्किल फ़ाइल पब्लिशर की रिपॉज़िटरी में ही रहती है।
कॉपी की गई कमांड टर्मिनल में पेस्ट करें। यह इस SKILL.md को उस एजेंट में इंस्टॉल करती है।
npx skills add inkeep/open-knowledge --skill review-a-design -a cursor -yकॉपी की गई कमांड टर्मिनल में पेस्ट करें। यह इस SKILL.md को उस एजेंट में इंस्टॉल करती है।
npx skills add inkeep/open-knowledge --skill review-a-design -a claude-code -yकॉपी की गई कमांड टर्मिनल में पेस्ट करें। यह इस SKILL.md को उस एजेंट में इंस्टॉल करती है।
npx skills add inkeep/open-knowledge --skill review-a-design -a codex -yकॉपी की गई कमांड टर्मिनल में पेस्ट करें। यह इस SKILL.md को उस एजेंट में इंस्टॉल करती है।
npx skills add inkeep/open-knowledge --skill review-a-design -a grok -yकॉपी किया गया संदेश Grok Bot चैट में भेजें। Bot यह SKILL.md GitHub से लाता है और उसे उन स्किल में जोड़ देता है जो आपके सभी Bot साझा करते हैं।
Install this skill: https://github.com/inkeep/open-knowledge/tree/HEAD/packages/server/assets/skills/packs/software-lifecycle/review-a-designपब्लिशर से
The platform /open-knowledge skill still governs every markdown operation here (reads via exec, writes via write/edit, links as plain relative markdown, MCP owns in-scope .md); this skill layers design-review craft on top of it.
Three reviews are not the same review, and only one is this skill's job.
You are doing the third. A proposal can be complete and factually correct and still be the wrong design — solving a symptom, chosen before its goals, engaging only strawman alternatives. Completeness and correctness are cheap to check and someone else's pass. Say this to the user up front if there's any ambiguity about what kind of review they want, then do soundness.
You produce findings, not edits. The author decides what to change. Never rewrite the artifact under review unless explicitly asked.
HARD GATE: never review a design you have not read end to end, and never review it in isolation from the decisions it inherits. A review of the first half is worse than no review — it spends the author's trust on partial understanding.
proposals/NNNN-name.md — Motivation / Design / Drawbacks / Alternatives / Unresolved questions),specs/NNN-name/spec.md — Goals / Non-goals / Design / Migration / Test plan, with a parent_proposal:),decisions/NNNN-title.md — Context / Decision / Consequences, with a supersedes: chain), orexec("cat proposals/0003-feature.md").parent_proposal:, and any proposal a decision implements;exec("grep -rln <subsystem-keyword> decisions/"), then cat the relevant ones. A design that contradicts an accepted ADR without noting it is a finding by itself.exec("ls -A postmortems/") and search({ query: "<subsystem> failure" }). A postmortem names a failure mode; a design that reintroduces it is your highest-value catch.supersedes: chain both directions.Read, Grep) — source is outside the knowledge base. In-scope markdown stays on exec/search.Do not proceed until you can name the goal, the constraints, and the prior decisions this design sits on top of.
Before you critique anything, state the design's argument in your own words: the goal it serves, the constraints it accepts, and why this design follows from them. Show it to the user before Step 2.
Why this gate exists:
For an in-flight choice with no document, this step is where you force the argument into words for the first time. Frequently the act of reconstruction resolves the question without a single lens.
Pass the design through each lens below. A lens is a named question plus the failure it catches — run the ones that bite for this artifact, skip the ones that plainly don't, and add any that earn their place. Do not mechanically fill all nine; a review that says the same shallow thing nine times teaches nothing.
Each finding has four parts, and a finding missing the second is an opinion — drop it:
the Design section says "[quoted text]" or [the Migration plan](./specs/012-sync/spec.md) assumes X. A finding with no evidence pointer is an opinion; delete it. This is the single discipline that separates a review the author acts on from one they resent.Rank by severity, not by reading order. Lead with the blocking findings; the author reads the top of your review and stops when they've got the gist. Burying the one blocking finding under six minor ones wastes it.
Before you deliver, turn the lenses on yourself. Reviews that flag everything teach the author to ignore reviews — the moment your review has one indefensible finding, the author discounts all of them.
In conversation by default. Most reviews are a message: the reconstructed argument (Step 1), the ranked findings (Step 3), the calibration notes (Step 4).
Persist as a document ONLY when the user asks, or the review is substantial enough to be cited later (a blocking review of a proposal heading to accept/reject). Then:
write({ document: { path: "proposals/0003-feature-review.md" } }).edit — a plain markdown link [design review](./0003-feature-review.md), never backticked, never an HTML anchor.Never edit the design under review to "apply" a finding. You emit findings; the authoring skill applies them.
Route blocking and substantive findings back to whoever owns the fix:
/frame-a-proposal (the argument, alternatives, or motivation needs rework)./write-a-spec (goals, non-goals, migration, or test plan needs rework)./record-a-decision, so the choice and its rationale land in decisions/ with a supersedes: link if it overturns a prior ADR.postmortems/YYYY-MM-DD-name.md so the design engages with it explicitly.Name the skill and the reason in your handoff so the author knows exactly where to go.
Reviews whether a design is SOUND — solving the right problem, derived from its stated goals and constraints — and emits ranked, evidence-backed findings, not edits. Read when asked to 'review this de
---name: review-a-designdescription: Reviews whether a design is SOUND — solving the right problem, derived from its stated goals and constraints —…---# packages/server/assets/skills/packs/software-lifecycle/review-a-design/SKILL.mdओवरव्यू
Reviews whether a design is SOUND — solving the right problem, derived from its stated goals and constraints — and emits ranked, evidence-backed findings, not edits. Read when asked to 'review this design', 'is this design sound', 'pressure-test this proposal', 'do a design review', 'does this solve the right problem', 'poke holes in this spec', 'should we build this', or to critique a proposal / spec / ADR / architecture or product decision. Do NOT read when the user wants to AUTHOR one of these — routing a new proposal is frame-a-proposal, a spec is write-a-spec, a decision record is record-a-decision, a postmortem is write-a-postmortem. Do NOT read for code review of a diff, or to fact-check individual claims (that is a correctness pass, a different job).
FAQ
पब्लिशर से packages/server/assets/skills/packs/software-lifecycle/review-a-design/SKILL.md डाउनलोड करें, या पाथ कॉपी करके रिपॉज़िटरी खोलें। PlugMCP स्किल को सूचीबद्ध करता है, फ़ाइल होस्ट नहीं करता।
पब्लिशर इसे https://github.com/inkeep/open-knowledge पर रखता है।
Claude, Cursor, Codex और Grok Build वह SKILL.md पढ़ सकते हैं जिसे आप पब्लिशर की रिपॉज़िटरी से जोड़ते हैं। जब आप चैट में स्किल के GitHub फ़ोल्डर का लिंक भेजते हैं, तो Grok Bot उसे इंस्टॉल कर देता है।