Extract implementation details and MVP versus Phase 2 distinctions from design documents.
npx skills add https://github.com/toshi-hm/dialy --skill revoiew-docs
Please help me install this Agent Skill. Skill: revoiew-docs Source: https://github.com/toshi-hm/dialy/tree/main/.claude/skills/review-docs Command: npx skills add https://github.com/toshi-hm/dialy --skill revoiew-docs
設計書に記載された要件を理解し、実装に必要な情報を抽出します。
指定された機能名を実行指示として渡すだけで、関連設計書から実装情報を抽出します。
High-intent search queries and answers about installing and using this skill.
To extract implementation details from design documents, you specify the target feature name, and the system identifies relevant sections across requirements, UI/UX, data models, and features to provide concrete implementation guidance.
Separating MVP requirements from Phase 2 features involves mapping design specs to actionable code guides, explicitly distinguishing MVP scope from the Phase 2 roadmap to ensure development clarity.
The best way to map design specs to actionable code guides is by identifying and extracting implementation details from requirements and data models, ensuring the extracted information translates directly into development instructions.
Yes, you can extract implementation guidance from multiple design documents, applying the process across requirements, UI/UX, data models, and features to ensure comprehensive MVP clarity and a Phase 2 roadmap.
No, you do not need to provide specific section names; passing the feature name as the execution instruction is sufficient to locate and extract the relevant implementation information from the design documents.
fosejaryConvert research and benchmarking into React Native MVP screen specs, navigation, and Supabase schemas.
alemdissoExecute a 5-checkpoint Phase 1 analysis for GitHub issues.
AustinZ21Convert dependency-ordered spec-kit tasks into GitHub issues.
jerome-benoitParse delta specs and generate a verification report with prioritized issues.
