plan
Scannednpx machina-cli add skill aiskillstore/marketplace/plan --openclawFiles (1)
SKILL.md
946 B
Task Planning
Workflow
- Gather Information: Explore codebase and list dependencies.
- Draft Plan:
- Objective: Goal of the task.
- Approach: High-level strategy.
- Steps: Sequential actions.
- Verification: How to prove it works.
- Clarify: Include at least 3 clarifying questions with proposed answers.
- Approve: Wait for user "go ahead" (empty response = approval).
- Implement: Execute only after approval.
Principles
- Zero-Impact: Do not modify files during planning.
- Iterative: Refine based on feedback.
- Concise: Keep plans readable and progress tracked via TODOs.
References
Source
git clone https://github.com/aiskillstore/marketplace/blob/main/skills/0xmsc/plan/SKILL.mdView on GitHub Overview
Plan helps teams align on non-trivial tasks and complex strategies before coding. It guides information gathering, a drafted plan with objective, approach, steps, and verification, followed by clarifications and an approval step to ensure alignment. Planning is zero-impact and iteratively refined.
How This Skill Works
Start by gathering information from the codebase and dependencies. Draft a plan containing Objective, Approach, Steps, and Verification. Include at least three clarifying questions with proposed answers, then wait for user approval (empty response = go ahead) before implementing. Do not modify files during planning; iterate based on feedback and track progress with TODOs.
When to Use It
- Planning a non-trivial feature or change that spans multiple components
- Aligning on a complex implementation strategy with stakeholders
- Before refactoring or architectural changes to assess risk and approach
- Coordinating changes across teams or modules with dependencies
- Validating constraints and dependencies before starting implementation
Quick Start
- Step 1: Gather information from the codebase and dependencies
- Step 2: Draft a plan with Objective, Approach, Steps, and Verification
- Step 3: Prepare at least 3 clarifying questions with proposed answers and await approval
Best Practices
- Gather information from the codebase and dependencies before drafting
- Draft a plan with clearly defined Objective, Approach, Steps, and Verification
- Include at least 3 clarifying questions with proposed answers
- Keep the plan zero-impact: do not modify files during planning
- Iterate on the plan and track progress with TODOs
Example Use Cases
- Plan adding a multi-service checkout flow that touches payments, inventory, and notifications
- Plan a UI/UX redesign requiring alignment with product goals and accessibility
- Plan a database migration with incremental steps and rollback verification
- Plan integration with a new third-party API, including rate limits and retries
- Plan a performance optimization with measurable verifications and rollback criteria
Frequently Asked Questions
Add this skill to your agents