docs: 초기 파일 추가 및 기본 설정 구성

- .git-commit-template.txt: 커밋 메시지 템플릿 추가
- .gitignore: OS 및 데이터베이스 관련 파일 무시 설정 추가
- .mcp.json: MCP 서버 설정 추가
- CLAUDE.md: SuperClaude 엔트리 포인트 문서 추가
- README.md: 프로젝트 템플릿 설명 추가
- .claude/COMMANDS.md: 명령어 실행 프레임워크 문서 추가
- .claude/FLAGS.md: 플래그 시스템 문서 추가
- .claude/MCP.md: MCP 서버 통합 문서 추가
- .claude/MODES.md: 운영 모드 문서 추가
- .claude/ORCHESTRATOR.md: 지능형 라우팅 시스템 문서 추가
- .claude/PERSONAS.md: 페르소나 시스템 문서 추가
- .claude/PRINCIPLES.md: 핵심 원칙 문서 추가
- .claude/RULES.md: 실행 가능한 규칙 문서 추가
- .claude/settings.json: 권한 설정 추가
- .claude/commands 디렉토리: 다양한 명령어 문서 추가
- .taskmaster/config.json: 기본 설정 파일 추가
- .taskmaster/docs 디렉토리: 문서 파일 추가
- .taskmaster/tasks/tasks.json: 기본 작업 파일 추가
This commit is contained in:
2025-07-20 22:25:33 +09:00
parent d9db49ee2e
commit c9020eb796
76 changed files with 13249 additions and 0 deletions

View File

@ -0,0 +1,113 @@
---
allowed-tools: [Read, Write]
description: Creates a PRD direction roadmap from a brainstorming session, suggesting phased PRD development for key features with improvement directions.
---
# Create PRD Direction Roadmap from Brainstorm
## Context
- User Request: $ARGUMENTS
- Brainstorm Session: Identified by --name argument (session name or index).
- Source Brainstorm: Final brainstorm-summary_*.md file from the specified brainstorm session directory.
- Roadmap Directory: .taskmaster/docs/roadmap/
## Goal
To transform creative ideas from a brainstorming session into a focused roadmap that suggests phased PRD development for key features, providing directions for iterative improvements without timelines or session states.
## Process
1. **Identify Source Brainstorm:**
- Use the --name argument to locate the correct brainstorm session directory (e.g., .taskmaster/docs/brainstorm/001-product-features/).
- Read the final brainstorm summary document (brainstorm-summary_*.md) to extract key concepts and ideas.
2. **Extract Key Elements from Brainstorm:**
- **Creative Insights:** Identify high-priority ideas and themes.
- **Feature Opportunities:** Map brainstorm concepts to potential features, prioritizing by innovation potential.
- **Improvement Directions:** For each feature, suggest iterative refinement paths (e.g., from initial idea to refined implementation).
3. **Generate PRD Direction Roadmap:**
- Create a single comprehensive document outlining phased PRD suggestions for features.
- Structure the content using the PRD Direction Roadmap Template, focusing on iterative PRD development and improvement suggestions.
- Ensure the roadmap emphasizes directions for PRD creation, such as evolving ideas through validation and refinement.
4. **Notify User with Key Insights:**
- Inform the user that the PRD direction roadmap has been generated.
- Provide the file path and highlight top feature suggestions.
- Suggest next steps: "Proceed to create detailed PRDs for suggested features using /planning/prd/2-create-from-brainstorm --name=[brainstorm_session_name] --feature=[feature_id]"
## Templates & Structures
### PRD Direction Roadmap Template
```markdown
# PRD Direction Roadmap: [Brainstorm Session Name]
**Created:** [Date]
**Source:** Brainstorm Session: [Brainstorm Session Name]
**Focus:** Phased PRD Development and Improvement Directions
---
## Executive Summary
- **Overview:** High-level suggestions for PRD development based on brainstorm ideas.
- **Key Features:** [Number] prioritized features with phased PRD directions.
- **Improvement Approach:** Iterative refinement from concepts to advanced implementations.
---
## Feature Suggestions
### Feature 1: [Feature Name]
- **Brainstorm Basis:** [Relevant ideas from brainstorm, e.g., innovative concepts].
- **Phased PRD Directions:**
- **Phase 1 (Core):** Basic PRD focusing on initial idea validation.
- **Phase 2 (Improvement):** Incorporate feedback for refinements.
- **Phase 3 (Advanced):** Add scalability and integration ideas.
- **Improvement Suggestions:** [e.g., Prototype testing, evolve based on user engagement metrics].
### Feature 2: [Feature Name]
- **Brainstorm Basis:** [Relevant ideas].
- **Phased PRD Directions:** [Similar phased structure].
- **Improvement Suggestions:** [Specific directions].
---
## Overall Improvement Strategy
- **Iteration Model:** Use brainstorm feedback to refine PRDs iteratively.
- **Prioritization Criteria:** Based on innovation impact and feasibility.
- **Success Indicators:** [e.g., Alignment with creative goals, measurable improvements].
---
## Next Steps
- Create PRD for Feature 1 using suggested directions.
- Validate improvements through prototypes or user tests.
```
## Best Practices / DO & DON'T
### ✅ DO: Focus on Iterative PRD Directions
- Emphasize phased approaches that guide PRD evolution from ideas to refinements.
- Suggest specific improvement ideas tied to brainstorm concepts.
**Why:** This ensures the roadmap drives actionable, evolving PRD creation.
### ✅ DO: Prioritize Based on Brainstorm Insights
- Rank features by creative impact and feasibility from the brainstorm.
- Include rationale for each suggestion.
**Why:** Maintains alignment with original innovative ideas.
### ❌ DON'T: Include Timelines or Deadlines
- Avoid any time-based planning or horizons.
**Why:** Focus solely on directional guidance for PRD development.
### ❌ DON'T: Add Unnecessary Complexity
- Keep suggestions concise and directly tied to PRD phases.
**Why:** The goal is to provide clear directions, not over-engineer the roadmap.
## Output
- **Format:** Markdown document.
- **Location:** .taskmaster/docs/roadmap/
- **Filename:** roadmap-prd-directions_[brainstorm_session_name].md
## Example Usage
- Create PRD direction roadmap from brainstorm session: /planning/roadmap/2-create-from-brainstorm --name="product-features"
- Create by brainstorm index: /planning/roadmap/2-create-from-brainstorm --name="1"