Initial commit
This commit is contained in:
12
.claude-plugin/plugin.json
Normal file
12
.claude-plugin/plugin.json
Normal file
@@ -0,0 +1,12 @@
|
|||||||
|
{
|
||||||
|
"name": "quick-plan-skill",
|
||||||
|
"description": "Create detailed engineering implementation plans for features or fixes based on user requirements. Generates comprehensive specifications with technical approach, step-by-step implementation, and testing strategy. Use when you need to plan before building, create detailed specs for complex features, or document the approach to solve a problem.",
|
||||||
|
"version": "1.0.0",
|
||||||
|
"author": {
|
||||||
|
"name": "Don Jacobsmeyer",
|
||||||
|
"email": "hello@donjacobsmeyer.com"
|
||||||
|
},
|
||||||
|
"skills": [
|
||||||
|
"./"
|
||||||
|
]
|
||||||
|
}
|
||||||
3
README.md
Normal file
3
README.md
Normal file
@@ -0,0 +1,3 @@
|
|||||||
|
# quick-plan-skill
|
||||||
|
|
||||||
|
Create detailed engineering implementation plans for features or fixes based on user requirements. Generates comprehensive specifications with technical approach, step-by-step implementation, and testing strategy. Use when you need to plan before building, create detailed specs for complex features, or document the approach to solve a problem.
|
||||||
72
SKILL.md
Normal file
72
SKILL.md
Normal file
@@ -0,0 +1,72 @@
|
|||||||
|
---
|
||||||
|
name: quick-plan-skill
|
||||||
|
description: Create detailed engineering implementation plans for features or fixes based on user requirements. Generates comprehensive specifications with technical approach, step-by-step implementation, and testing strategy. Use when you need to plan before building, create detailed specs for complex features, or document the approach to solve a problem.
|
||||||
|
allowed-tools: Read, Write, Edit, Glob, Grep
|
||||||
|
---
|
||||||
|
|
||||||
|
# Quick Plan
|
||||||
|
|
||||||
|
Create comprehensive implementation plans that serve as blueprints for actual development work. This skill analyzes requirements, thinks through the approach, and generates a detailed specification document.
|
||||||
|
|
||||||
|
## Prerequisites
|
||||||
|
|
||||||
|
- Clear description of what needs to be built or fixed
|
||||||
|
- Understanding of the codebase structure (run `/prime` first if needed)
|
||||||
|
- Time to think through the technical approach
|
||||||
|
|
||||||
|
## Workflow
|
||||||
|
|
||||||
|
1. **Analyze requirements** - Parse the user's request deeply
|
||||||
|
2. **Design solution** - Think through technical approach and architecture
|
||||||
|
3. **Document plan** - Create comprehensive markdown specification
|
||||||
|
4. **Generate filename** - Create descriptive kebab-case filename
|
||||||
|
5. **Save and report** - Write to `specs/` directory with summary
|
||||||
|
|
||||||
|
## Instructions
|
||||||
|
|
||||||
|
When creating a plan:
|
||||||
|
|
||||||
|
1. **Problem Statement** - Clearly state what the user wants to build/fix
|
||||||
|
2. **Objectives** - List specific, measurable objectives
|
||||||
|
3. **Technical Approach** - Describe architecture decisions and why
|
||||||
|
4. **Implementation Steps** - Step-by-step guide another dev could follow
|
||||||
|
5. **Code Examples** - Include pseudo-code or examples for complex parts
|
||||||
|
6. **Edge Cases** - Consider error handling and scalability
|
||||||
|
7. **Testing Strategy** - How to validate the implementation
|
||||||
|
8. **Success Criteria** - How to know it's done
|
||||||
|
|
||||||
|
Output format:
|
||||||
|
- Use proper markdown with clear sections
|
||||||
|
- Include code examples or pseudo-code
|
||||||
|
- Consider edge cases and error handling
|
||||||
|
- Save to `specs/<descriptive-name>.md` with kebab-case naming
|
||||||
|
- Make it detailed enough that another developer could implement it
|
||||||
|
|
||||||
|
## Examples
|
||||||
|
|
||||||
|
**Example 1: Planning a feature**
|
||||||
|
```
|
||||||
|
User: Create a plan for adding dark mode support
|
||||||
|
Claude: [Analyzes requirements]
|
||||||
|
[Designs technical approach]
|
||||||
|
[Creates comprehensive plan]
|
||||||
|
File: specs/dark-mode-implementation.md
|
||||||
|
Key Components:
|
||||||
|
- Theme context provider
|
||||||
|
- CSS variable system
|
||||||
|
- localStorage persistence
|
||||||
|
- Component theme switching
|
||||||
|
```
|
||||||
|
|
||||||
|
**Example 2: Planning a refactor**
|
||||||
|
```
|
||||||
|
User: Plan how to refactor our authentication system to use OAuth2
|
||||||
|
Claude: [Analyzes current system and requirements]
|
||||||
|
[Designs OAuth2 integration approach]
|
||||||
|
File: specs/oauth2-migration.md
|
||||||
|
Key Components:
|
||||||
|
- OAuth provider setup
|
||||||
|
- Token management
|
||||||
|
- User migration strategy
|
||||||
|
- Fallback for existing sessions
|
||||||
|
```
|
||||||
45
plugin.lock.json
Normal file
45
plugin.lock.json
Normal file
@@ -0,0 +1,45 @@
|
|||||||
|
{
|
||||||
|
"$schema": "internal://schemas/plugin.lock.v1.json",
|
||||||
|
"pluginId": "gh:djacobsmeyer/claude-skills-engineering:plugins/quick-plan-skill",
|
||||||
|
"normalized": {
|
||||||
|
"repo": null,
|
||||||
|
"ref": "refs/tags/v20251128.0",
|
||||||
|
"commit": "d3bd26f6ddd5a90df07b774d46867f08eee1b8f8",
|
||||||
|
"treeHash": "35461daf4a347f006800b164ff29dd9ec85b235cec833498b988371e4e26e2e6",
|
||||||
|
"generatedAt": "2025-11-28T10:16:28.696642Z",
|
||||||
|
"toolVersion": "publish_plugins.py@0.2.0"
|
||||||
|
},
|
||||||
|
"origin": {
|
||||||
|
"remote": "git@github.com:zhongweili/42plugin-data.git",
|
||||||
|
"branch": "master",
|
||||||
|
"commit": "aa1497ed0949fd50e99e70d6324a29c5b34f9390",
|
||||||
|
"repoRoot": "/Users/zhongweili/projects/openmind/42plugin-data"
|
||||||
|
},
|
||||||
|
"manifest": {
|
||||||
|
"name": "quick-plan-skill",
|
||||||
|
"description": "Create detailed engineering implementation plans for features or fixes based on user requirements. Generates comprehensive specifications with technical approach, step-by-step implementation, and testing strategy. Use when you need to plan before building, create detailed specs for complex features, or document the approach to solve a problem.",
|
||||||
|
"version": "1.0.0"
|
||||||
|
},
|
||||||
|
"content": {
|
||||||
|
"files": [
|
||||||
|
{
|
||||||
|
"path": "README.md",
|
||||||
|
"sha256": "813edb8ce7785bfc3b60144b943f27286c51ee9dabf0db5c2b7aefb30871ae74"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"path": "SKILL.md",
|
||||||
|
"sha256": "214264d7d07349f358ec08f430eeba21362c67f59f833b874639aae168886704"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"path": ".claude-plugin/plugin.json",
|
||||||
|
"sha256": "09df18ddc55187202aabca07e0cf848c015197b0c31036a34e91d0959f28f277"
|
||||||
|
}
|
||||||
|
],
|
||||||
|
"dirSha256": "35461daf4a347f006800b164ff29dd9ec85b235cec833498b988371e4e26e2e6"
|
||||||
|
},
|
||||||
|
"security": {
|
||||||
|
"scannedAt": null,
|
||||||
|
"scannerVersion": null,
|
||||||
|
"flags": []
|
||||||
|
}
|
||||||
|
}
|
||||||
Reference in New Issue
Block a user