Identify gaps and drift between product.md and solution.md before development.
npx skills add https://github.com/daddia/space --skill review-docs-daddia
Please help me install this Agent Skill. Skill: review-docs Source: https://github.com/daddia/space/tree/main/.agents/skills/review-docs Command: npx skills add https://github.com/daddia/space --skill review-docs-daddia
Reviews product.md and solution.md for completeness and alignment before development begins. Use to confirm that goals, context, and decisions are consistent across documents, and to flag gaps, inconsistencies, and drift between the two documents. Do NOT use to review code — use review-code for that. Do NOT use to review an ADR — use review-adr.
Invoke the Review Docs skill against your target epic to start the pre-sprint documentation review.
High-intent search queries and answers about installing and using this skill.
To review product and solution documentation for alignment, you need to identify gaps and drift between product.md and solution.md files. This verifies that goals, context, and decisions are consistent across both documents before development begins.
Documentation drift in pre-sprint planning refers to inconsistencies and misalignment that develop between product.md and solution.md files. Detecting this drift ensures complete, consistent framing of the epic and confirms end-to-end readiness before development starts.
To check prerequisites and readiness for epic-level documentation, validate the consumes and produces outputs of both product.md and solution.md. This prerequisite and output check confirms end-to-end readiness before development begins.
No, you cannot use this approach to review code or architecture decision records. This documentation review specifically targets gaps between product.md and solution.md; you must use dedicated code or ADR review processes for those files.
Architects and PMs align expectations before a foundation sprint by generating a review summary that highlights blocking issues and actionable next steps. This guides in-place remediation by adding TODO notes or direct edits to resolve documentation gaps.
The best way to flag inconsistencies between product and solution docs is to perform a structured review that identifies gaps and drift, appending a formal review section to the most affected document to guide in-place amendments and remediation.
SylphxAIManages deployments with safe rollbacks and feature flags in production.
trycompaiCategorize OpenAPI SDK generation failures and propose remediation steps.
ondrej-svecCross-reference code against design docs and produce ADR-backed architecture review documents.
FrogAiMap achievement signals from Jira, GitHub, and Slack to ladder criteria for readiness gaps.
