Initial commit: Chat-to-diagram v1.0
- Chat interface with OpenAI GPT integration - Automatic diagram generation from text descriptions - Tldraw canvas with Dagre layout engine - REST API instead of WebSocket approach 🤖 Generated with Claude Code (https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
This commit is contained in:
204
.claude/commands/create-plan.md
Normal file
204
.claude/commands/create-plan.md
Normal file
@@ -0,0 +1,204 @@
|
||||
---
|
||||
description: Create a comprehensive implementation plan from requirements document through extensive research
|
||||
argument-hint: [plan-description-or-requirements-file]
|
||||
---
|
||||
|
||||
# Create Implementation Plan from Requirements
|
||||
|
||||
You are about to create a comprehensive implementation plan based on initial requirements. This involves extensive research, analysis, and planning to produce a detailed roadmap for execution.
|
||||
|
||||
IMPORTANT: The plan should be between 500 and 1000 lines.
|
||||
|
||||
## Step 1: Read and Analyze Requirements
|
||||
|
||||
Understand the requirements or read the requirements document from: $ARGUMENTS
|
||||
|
||||
Extract and understand:
|
||||
- Core feature requests and objectives
|
||||
- Technical requirements and constraints
|
||||
- Expected outcomes and success criteria
|
||||
- Integration points with existing systems
|
||||
- Performance and scalability requirements
|
||||
- Any specific technologies or frameworks mentioned
|
||||
|
||||
## Step 2: Research Phase
|
||||
|
||||
### 2.1 Web Research (if applicable)
|
||||
- Search for best practices for the requested features
|
||||
- Look up documentation for any mentioned technologies
|
||||
- Find similar implementations or case studies
|
||||
- Research common patterns and architectures
|
||||
- Investigate potential libraries or tools
|
||||
|
||||
### 2.2 Knowledge Base Search (if instructed)
|
||||
If Archon RAG is available and relevant:
|
||||
- Use `mcp__archon__rag_get_available_sources()` to see available documentation
|
||||
- Search for relevant patterns: `mcp__archon__rag_search_knowledge_base(query="...")`
|
||||
- Find code examples: `mcp__archon__rag_search_code_examples(query="...")`
|
||||
- Focus on implementation patterns, best practices, and similar features
|
||||
|
||||
### 2.3 Codebase Analysis (for existing projects)
|
||||
If this is for an existing codebase:
|
||||
|
||||
**IMPORTANT: Use the `codebase-analyst` agent for deep pattern analysis**
|
||||
- Launch the codebase-analyst agent using the Task tool to perform comprehensive pattern discovery
|
||||
- The agent will analyze: architecture patterns, coding conventions, testing approaches, and similar implementations
|
||||
- Use the agent's findings to ensure your plan follows existing patterns and conventions
|
||||
|
||||
For quick searches you can also:
|
||||
- Use Grep to find specific features or patterns
|
||||
- Identify the project structure and conventions
|
||||
- Locate relevant modules and components
|
||||
- Understand existing architecture and design patterns
|
||||
- Find integration points for new features
|
||||
- Check for existing utilities or helpers to reuse
|
||||
|
||||
## Step 3: Planning and Design
|
||||
|
||||
Based on your research, create a detailed plan that includes:
|
||||
|
||||
### 3.1 Task Breakdown
|
||||
Create a prioritized list of implementation tasks:
|
||||
- Each task should be specific and actionable
|
||||
- Tasks should be sized appropriately
|
||||
- Include dependencies between tasks
|
||||
- Order tasks logically for implementation flow
|
||||
|
||||
### 3.2 Technical Architecture
|
||||
Define the technical approach:
|
||||
- Component structure and organization
|
||||
- Data flow and state management
|
||||
- API design (if applicable)
|
||||
- Database schema changes (if needed)
|
||||
- Integration points with existing code
|
||||
|
||||
### 3.3 Implementation References
|
||||
Document key resources for implementation:
|
||||
- Existing code files to reference or modify
|
||||
- Documentation links for technologies used
|
||||
- Code examples from research
|
||||
- Patterns to follow from the codebase
|
||||
- Libraries or dependencies to add
|
||||
|
||||
## Step 4: Create the Plan Document
|
||||
|
||||
Write a comprehensive plan to `PRPs/requests/[feature-name].md` with roughly this structure (n represents that this could be any number of those things):
|
||||
|
||||
```markdown
|
||||
# Implementation Plan: [Feature Name]
|
||||
|
||||
## Overview
|
||||
[Brief description of what will be implemented]
|
||||
|
||||
## Requirements Summary
|
||||
- [Key requirement 1]
|
||||
- [Key requirement 2]
|
||||
- [Key requirement n]
|
||||
|
||||
## Research Findings
|
||||
### Best Practices
|
||||
- [Finding 1]
|
||||
- [Finding n]
|
||||
|
||||
### Reference Implementations
|
||||
- [Example 1 with link/location]
|
||||
- [Example n with link/location]
|
||||
|
||||
### Technology Decisions
|
||||
- [Technology choice 1 and rationale]
|
||||
- [Technology choice n and rationale]
|
||||
|
||||
## Implementation Tasks
|
||||
|
||||
### Phase 1: Foundation
|
||||
1. **Task Name**
|
||||
- Description: [What needs to be done]
|
||||
- Files to modify/create: [List files]
|
||||
- Dependencies: [Any prerequisites]
|
||||
- Estimated effort: [time estimate]
|
||||
|
||||
2. **Task Name**
|
||||
- Description: [What needs to be done]
|
||||
- Files to modify/create: [List files]
|
||||
- Dependencies: [Any prerequisites]
|
||||
- Estimated effort: [time estimate]
|
||||
|
||||
### Phase 2: Core Implementation
|
||||
[Continue with numbered tasks...]
|
||||
|
||||
### Phase 3: Integration & Testing
|
||||
[Continue with numbered tasks...]
|
||||
|
||||
## Codebase Integration Points
|
||||
### Files to Modify
|
||||
- `path/to/file1.js` - [What changes needed]
|
||||
- `path/to/filen.py` - [What changes needed]
|
||||
|
||||
### New Files to Create
|
||||
- `path/to/newfile1.js` - [Purpose]
|
||||
- `path/to/newfilen.py` - [Purpose]
|
||||
|
||||
### Existing Patterns to Follow
|
||||
- [Pattern 1 from codebase]
|
||||
- [Pattern n from codebase]
|
||||
|
||||
## Technical Design
|
||||
|
||||
### Architecture Diagram (if applicable)
|
||||
```
|
||||
[ASCII diagram or description]
|
||||
```
|
||||
|
||||
### Data Flow
|
||||
[Description of how data flows through the feature]
|
||||
|
||||
### API Endpoints (if applicable)
|
||||
- `POST /api/endpoint` - [Purpose]
|
||||
- `GET /api/endpoint/:id` - [Purpose]
|
||||
|
||||
## Dependencies and Libraries
|
||||
- [Library 1] - [Purpose]
|
||||
- [Library n] - [Purpose]
|
||||
|
||||
## Testing Strategy
|
||||
- Unit tests for [components]
|
||||
- Integration tests for [workflows]
|
||||
- Edge cases to cover: [list]
|
||||
|
||||
## Success Criteria
|
||||
- [ ] [Criterion 1]
|
||||
- [ ] [Criterion 2]
|
||||
- [ ] [Criterion n]
|
||||
|
||||
## Notes and Considerations
|
||||
- [Any important notes]
|
||||
- [Potential challenges]
|
||||
- [Future enhancements]
|
||||
|
||||
---
|
||||
*This plan is ready for execution with `/execute-plan`*
|
||||
```
|
||||
|
||||
## Step 5: Validation
|
||||
|
||||
Before finalizing the plan:
|
||||
1. Ensure all requirements are addressed
|
||||
2. Verify tasks are properly sequenced
|
||||
3. Check that integration points are identified
|
||||
4. Confirm research supports the approach
|
||||
5. Make sure the plan is actionable and clear
|
||||
|
||||
## Important Guidelines
|
||||
|
||||
- **Be thorough in research**: The quality of the plan depends on understanding best practices
|
||||
- **Keep it actionable**: Every task should be clear and implementable
|
||||
- **Reference everything**: Include links, file paths, and examples
|
||||
- **Consider the existing codebase**: Follow established patterns and conventions
|
||||
- **Think about testing**: Include testing tasks in the plan
|
||||
- **Size tasks appropriately**: Not too large, not too granular
|
||||
|
||||
## Output
|
||||
|
||||
Save the plan to the PRPs/requests/ directory and inform the user:
|
||||
"Implementation plan created at: PRPs/requests/[feature-name].md
|
||||
You can now execute this plan using: `/execute-plan PRPs/requests/[feature-name].md`"
|
||||
Reference in New Issue
Block a user