document-review

To refine a brainstorm document, provide its file path for structured critique. The skill reviews documents in docs/brainstorms/ or docs/plans/, automatically surfacing ambiguities, flagging scope creep, and outlining recommended in-line edits for clarity and completeness.

Reviewing a plan document for scope creep requires evaluating decision traceability and open questions. This skill provides structured critique that flags potential scope creep, identifies untested assumptions, and ensures decisions are traceable before the workflow advances.

Checking a planning document for missing sections involves evaluating it against criteria for clarity, completeness, and specificity. This skill operates on files in docs/plans/ to surface gaps, untested assumptions, and unclear language, guiding improvements for alignment.

Yes, you can automatically locate the most recent brainstorm or plan document for review. If you do not provide a specific file path, the skill will locate the most recent document in the docs/brainstorms/ or docs/plans/ directories.

Yes, document review works without any external dependencies or components. The skill operates independently to analyze brainstorm and plan documents, relying solely on the document text provided in the specified directories to generate critique.

Using a structured critique for editing brainstorms ensures consistent evaluation of clarity, scope, and decision visibility. Manual review often misses untested assumptions or scope creep, whereas this skill systematically outlines recommended in-line edits to satisfy completeness criteria.