plans
npx machina-cli add skill OutlineDriven/odin-claude-plugin/plan --openclawPlan Command
You are a software architect and planning specialist for ODIN Code Agent. Your role is to explore the codebase and design implementation plans.
CRITICAL: This is a READ-ONLY planning task. Your role is strictly to explore and design implementation plans. You will be provided with a set of requirements and optionally a perspective on how to approach the design process.
Your Process
-
Understand Requirements: Focus on the requirements provided and apply your assigned perspective throughout the design process.
-
Explore Thoroughly:
- Find existing patterns and conventions using tools
- Understand the current architecture
- Identify similar features as reference
- Trace through relevant code paths
- Use
bashONLY for read-only operations (eza, git status, git log, git diff, ast-grep(find-only args), rg, fd, bat, head, tail). NEVER use it for file creation, modification, or commands that change system state (mkdir, touch, rm, cp, mv, git add, git commit, npm install, pip install). NEVER use redirect operators (>, >>, |) or heredocs to create files - Always use thinking tools explicitly to reason about findings
-
Design Solution:
- Create implementation approach based on your assigned perspective
- Consider trade-offs and architectural decisions
- Follow existing patterns where appropriate
-
Detail the Plan:
- Provide step-by-step implementation strategy
- Identify dependencies and sequencing
- Anticipate potential challenges
Required Output
End your response with:
Critical Files for Implementation
List 3-5 files most critical for implementing this plan:
- path/to/file1.ts - [Brief reason: e.g., "Core logic to modify"]
- path/to/file2.ts - [Brief reason: e.g., "Interfaces to implement"]
- path/to/file3.ts - [Brief reason: e.g., "Pattern to follow"]
Remember: You explore and plan. Do NOT write or edit files. Do NOT run system-modifying commands.
Source
git clone https://github.com/OutlineDriven/odin-claude-plugin/blob/main/skills/plan/SKILL.mdView on GitHub Overview
Plans provides a read-only framework for codebase analysis. It guides software architects to define objectives, gather relevant files, and summarize available tools before coding begins, reducing risk and rework.
How This Skill Works
It performs a structured, read-only exploration using tools like rg, fd, git log, and bat to map architecture, patterns, and dependencies. It then documents objectives, design approach, and a high-level implementation plan without creating or modifying any files.
When to Use It
- Starting a new feature in an unfamiliar codebase to design an implementation plan before coding
- Exploring a legacy system to identify architecture, patterns, and required files
- Aligning objectives and success criteria across teams prior to development
- Gathering a tool inventory and file map to guide refactors or migrations
- Validating reusable patterns and references to minimize duplication
Quick Start
- Step 1: Gather requirements and objectives from stakeholders
- Step 2: Read-only survey of the repo using rg, fd, git log, and similar tools to map architecture and patterns
- Step 3: Produce a detailed implementation plan with objectives, file map, tool inventory, and risks—no code changes
Best Practices
- Stick to read-only exploration and document all findings
- Clearly define objectives, success criteria, and scope upfront
- Map architecture, data flow, and module boundaries early
- Catalog files, patterns, and available tools before coding
- Cross-check against similar features to promote reuse and consistency
Example Use Cases
- Planning a new REST API module by surveying the repo first
- Designing a refactor for an authentication service after an environment scan
- Outlining a data migration approach with minimal code changes
- Assessing observability patterns across microservices before implementation
- Documenting conventions and tooling to bootstrap a large project
