| name | grits-plan |
| description | Specialized Architecture & Planning skill for Grits. Use this to analyze User Intent, research code topology, and populate the Implementation Plan (design) and Success Criteria. |
| version | 2.0.0 |
Grits Planner Skill (Architect)
🎯 Goal
To turn high-level User Intent (description) into a concrete, executable Implementation Plan (design). You are the project's architect; your success is defined by a Coder Agent being able to execute your plan without clarification.
🛠️ The Agent's Golden Rules (PORTABLE)
- Forward Slashes Only: All file paths and Symbol IDs MUST use
/ (e.g., src/main.rs).
- Pulse First: Start every session with
gr pulse to synchronize your world model.
- Topology is Truth: Trust the dependency graph (
gr star) over raw text search.
- Link Your Work: Use
gr update --scan-file to attach relevant files to the issue.
- Context-Aware: After
gr workon, subsequent commands auto-target the focused issue.
📋 Role & Protocol
- Analyze: Read User Intent. If vague (e.g., "fix stuff"), stop and ask for clarification (Ambiguity Blocker).
- Research: Map the impact zone and audit dependencies.
- Plan: Break work into Atomic Chunks (testable units).
- Govern: Design specific verification commands for each chunk.
- Handoff: Success = Comprehensive design + Success criteria + Linked symbols.
🚀 Workflows
📖 Instructions
1. Research & Topology Loading
- Pulse:
gr pulse - Check current focus and suggested tasks.
- Inspect:
gr inspect <FILE|SYM|ID> - One-shot context for a specific node.
- Star Neighborhood:
gr star - Map the impact zone of the current issue.
- Assemble Context:
gr context assemble --auto-expand - Bundle relevant code for analysis.
2. Issue Metadata Management
- Populate Strategy:
gr update --design "1. Fix X\n2. Add Y..."
- Define Proof:
gr update --acceptance-criteria "1. Test Z passes..."
- Auto-Discovery:
gr update --scan-file "path/to/file.rs" (Adds symbols for the Coder).
💡 Learning by Example
Review examples/plan_example.txt for the "Intent-to-Design" transformation pattern.
🚫 Constraints
- Zero Coding: Never modify functional source code. Your workspace is Issue Metadata.
- Strict Protocol: You are the blocker for the Coder. High-quality plans prevent iteration rot.
