Simulate a review panel to assess blueprint quality and issues.
npx skills add https://github.com/wrteam-jay/blueprint --skill review-wrteam-jay
Please help me install this Agent Skill. Skill: review Source: https://github.com/wrteam-jay/blueprint/tree/main/skills/blueprint/skills/review Command: npx skills add https://github.com/wrteam-jay/blueprint --skill review-wrteam-jay
This Skill addresses the friction in product development caused by tribal knowledge, terminology drift, and a lack of a shared reference, ensuring that system specifications are clear, complete, and consistently understood by the entire team.
review skill to have the AI simulate a panel discussion, identifying any ambiguities or missing information before the design is finalized.Use the review skill to evaluate the blueprint located at /path/to/blueprint/SKILL.md.
High-intent search queries and answers about installing and using this skill.
Evaluating a blueprint for completeness involves checking for terminology consistency, domain model clarity, and scenario coverage. A structured review panel can simulate a debate to pinpoint implementation leakage and open questions, ensuring the specification serves as a reliable single source of truth.
To check a draft specification for implementation leakage and open questions, facilitate a structured debate with a simulated review panel. This evaluation specifically targets requirements quality and domain model clarity to ensure the blueprint remains clear and consistently understood by the team.
The best way to ensure team alignment on a product feature specification is to evaluate the draft against quality assurance criteria like scenario coverage and terminology consistency. A structured review process resolves friction caused by tribal knowledge and terminology drift.
Yes, you can use a simulated review panel to assess an existing system specification. The review process evaluates the blueprint for clarity, completeness, and adherence to format, addressing any issues related to terminology and domain model clarity to maintain a shared reference.
You need to perform a structured debate on a blueprint after drafting a new feature specification and before the design is finalized. This ensures the document is evaluated for scenario coverage and requirements quality, preventing tribal knowledge from causing friction in product development.
dev-goraebapExtracts minimum viable information from requirements documents to bootstrap an FSD blueprint.
kunalrawat425Propose a cohesive design system and generate a DESIGN.md source of truth.
eai-toolsExtract domain terminology from project documentation into feature glossaries.
Chang-Shih-YungAggregate type checker, linter, and test results into a 0-10 composite score.