Initial commit: antigravity-claudekit
This commit is contained in:
49
skills/ck-plan/SKILL.md
Normal file
49
skills/ck-plan/SKILL.md
Normal file
@@ -0,0 +1,49 @@
|
||||
---
|
||||
name: ck-plan
|
||||
description: Create an intelligent implementation plan with prompt enhancement. Use when planning a feature, designing architecture, starting a new task, or creating a detailed phased implementation roadmap.
|
||||
---
|
||||
|
||||
# Plan — Intelligent Plan Creation
|
||||
|
||||
Creates enhanced implementation plans with prompt improvement before planning.
|
||||
|
||||
## When to Use
|
||||
|
||||
- Starting a new feature or task that needs structured planning
|
||||
- Designing system architecture with phased implementation
|
||||
- Creating a roadmap before delegating to implementation agents
|
||||
|
||||
## Don't Use When
|
||||
|
||||
- Task is trivial and needs no plan (just implement directly)
|
||||
- An active plan already exists and implementation is underway
|
||||
|
||||
## Pre-Creation Check
|
||||
|
||||
Check the `## Plan Context` section injected by session hooks:
|
||||
- **Active plan path shown** → ask user: "Active plan found: {path}. Continue with this? [Y/n]"
|
||||
- **Suggested path shown** → ask user if they want to activate it or create new
|
||||
- **"Plan: none"** → proceed to create new plan using naming pattern from `## Naming` section
|
||||
|
||||
## Workflow
|
||||
|
||||
1. Analyze the task — ask clarifying questions if requirements are unclear
|
||||
2. Decide complexity: simple task → `ck-plan-fast`; complex task → `ck-plan-hard`
|
||||
3. Enhance the prompt — expand the task description with full context and details
|
||||
4. Execute the appropriate planning skill with the enhanced prompt
|
||||
5. Activate the `planning` skill to structure the plan output
|
||||
|
||||
## Planning Modes
|
||||
|
||||
| Mode | When to Use |
|
||||
|------|-------------|
|
||||
| `ck-plan-fast` | Clear requirements, straightforward implementation, no research needed |
|
||||
| `ck-plan-hard` | Complex architecture, unclear requirements, needs research |
|
||||
| `ck-plan-parallel` | Large feature benefiting from parallel execution phases |
|
||||
|
||||
## Important Rules
|
||||
|
||||
- Do NOT start implementing — planning only
|
||||
- Sacrifice grammar for concision in plan output
|
||||
- List unresolved questions at the end of the plan
|
||||
- Ensure token efficiency while maintaining quality
|
||||
Reference in New Issue
Block a user