bostonaholic/skills

reviewing-design-docs

Reviews a technical design document or RFC adversarially in a fresh-context read-only subagent (coverage, decisions, edge cases, consistency, risks, citations, scope) and returns findings with a verdict.

Voir la source

Mode d’emploi

  1. Copiez la commande et examinez le paquet avant de l’installer dans votre environnement agent.
  2. Consultez le document original pour les outils, identifiants et environnements requis.
  3. Décrivez les entrées et le livrable souhaité ; comparez la sortie aux sources.
npx skills add https://github.com/bostonaholic/skills --skill reviewing-design-docs

Avant de commencer

  • L’installation n’inclut ni abonnement au modèle, ni quota API, ni accès aux fichiers.
  • Étoiles et installations reflètent l’activité, pas un test indépendant de qualité ou de sécurité.
Document Skill original

Rendu depuis le dépôt source en conservant titres, exemples, code, tableaux, liens et images.

Engineering Design Doc Review

Input

$ARGUMENTS is the path to one design document. When it is a URL or pasted text, save it as Markdown in a scratch file outside the repository and review that path; when a fetch fails, report the URL and the error. When the argument is empty, names a directory, or names no readable file, ask for the path and wait. Never guess.

Reviewer

This session holds the author's conversation, so it cannot review the document (independent review rules). Run the design reviewer brief in a fresh-context subagent with read and search tools only, giving it the document's absolute path and the paths of the files the brief links: design template, finding format, and decision-record rules. Pass no author discussion. If no such subagent can run, stop and say so. Never review inline.

Verdict and relay

The report's first line must be exactly **Verdict: APPROVE**, **Verdict: REQUEST CHANGES**, or **Verdict: COMMENT**. When it is missing or wrong, run one new reviewer with the same inputs and name the failed contract. When the second report also fails, print it, name the failure, and stop. Never repair a verdict yourself.

Print the report verbatim. When the read-only restriction rested on the reviewer's prompt rather than its tool grants, say so in one line after the report. Do not revise the document; on REQUEST CHANGES the user decides how. Write no file beyond the scratch copy.

Tâches connexes

du même dépôt

Autres Skills

Tous les Skills
bostonaholic
Communauté

auditing-complexity

Ranks where code complexity concentrates in a git repository (cyclomatic complexity, nesting, fan-out, mutable state) and scores CRAP change risk from a coverage file. Read-only. Use when asked for complexity hotspots or change risk. Not for test value; use auditing-tests.

Installations / 1h
1
GitHub Stars
2
Mis à jour
20 oct.
bostonaholic
Communauté

composing-agent-prompts

Composes a self-contained, source-cited task prompt for another coding agent to execute in a target repository, without running the task. Use when the user asks to write, draft, or hand off a prompt, brief, or task spec for another agent. Not for system prompts; use writing-system-prompts.

Installations / 1h
1
GitHub Stars
2
Mis à jour
20 oct.
bostonaholic
Communauté

conducting-deep-research

Conducts source-backed, goal-directed research that combines a scholarly evidence review with an institution, company, or funding map. Use when a request needs both an evidence review and an organization or funding map. Not for quick lookups or general research write-ups.

Installations / 1h
1
GitHub Stars
2
Mis à jour
20 oct.
bostonaholic
Communauté

cutting-skills

Audits or trims an existing agent skill to its behavioral core and narrows over-broad trigger metadata. Use when the user asks to cut, simplify, shorten, de-slop, or reduce the context cost or trigger aggressiveness of a SKILL.md or skill folder. Never infer from a skill being long or edited for another purpose.

Installations / 1h
1
GitHub Stars
2
Mis à jour
20 oct.