agile-design-doc
Generate Agile Design Documents
Development teams need concise design documents that align with MVP principles and avoid over-engineering. This skill generates focused, technical design documents with Mermaid diagrams, implementation details, and clear success criteria.
スキルZIPをダウンロード
Claudeでアップロード
設定 → 機能 → スキル → スキルをアップロードへ移動
オンにして利用開始
テストする
「agile-design-doc」を使用しています。 Generate a design document for a user authentication feature in a Python Flask application
期待される結果:
- Design Document: User Authentication
- Target: Flask-based REST API
- Key Features: Login, Register, Token Refresh
- Mermaid sequence diagram showing auth flow
- Code examples for auth endpoints
「agile-design-doc」を使用しています。 Create a design doc for a payment processing module integration
期待される結果:
- Payment Module Integration Design
- Data Models: Order, Payment, Transaction
- API Endpoints with request/response schemas
- Sequence diagram: Order -> Payment Gateway -> Callback
- Error handling and retry strategies
セキュリティ監査
安全Security audit completed. All 39 static findings are false positives. The skill contains only markdown documentation templates with example code blocks (Python, JSON, Mermaid diagrams). No actual code execution, cryptographic algorithms, or malicious patterns exist. This is a legitimate documentation generation skill for agile development teams.
高リスクの問題 (2)
中リスクの問題 (1)
低リスクの問題 (1)
品質スコア
作れるもの
Quick Design Sprint
Rapidly generate a design document for a new feature during sprint planning
Cross-Team Alignment
Create standardized design documents that help backend, frontend, and QA teams understand requirements
Technical Documentation
Generate reference documentation for existing system modules
これらのプロンプトを試す
Generate a design document for a new [feature name] feature. The feature should [brief description]. Consider using [tech stack].
Create a design document for a REST API that handles [resource]. Include data models, endpoints, and sequence diagrams.
Generate a design document showing how to integrate [new module] with the existing [existing system]. Show the interaction flow.
Design the data models and relationships for [domain area]. Include key entities, attributes, and how they interact.
ベストプラクティス
- Start by analyzing the existing tech stack from project configuration files
- Focus on MVP scope - document core functionality first
- Use Mermaid diagrams to visualize component interactions
- Include code examples for critical implementation paths
回避
- Adding unnecessary features that could be deferred to later iterations
- Writing lengthy background explanations instead of focusing on implementation
- Ignoring existing components and duplicating functionality
- Including every possible edge case instead of focusing on happy paths