{"skill":{"slug":"plans-methodology","displayName":"Plans Methodology","summary":"Structured work tracking methodology using Plans. Use when creating, managing, reviewing, or delegating plans for significant work. Covers plan lifecycle (dr...","description":"---\nname: plans-methodology\ndescription: Structured work tracking methodology using Plans. Use when creating, managing, reviewing, or delegating plans for significant work. Covers plan lifecycle (draft, approved, in_progress, completed, archived), folder structure, approval authority, cross-agent delegation, and task tracking. Use when a user asks to create a plan, track work, delegate tasks to sub-agents, or review plan status.\n---\n\n# Plans Methodology\n\nStructured work tracking for individuals or multi-agent teams. Each agent maintains `plans/` in their workspace.\n\n## Directory Structure\n\n```\nplans/\n  README.md\n  draft/          # Being defined, not yet approved\n  approved/       # Ready for execution\n  in_progress/    # Currently executing\n  completed/      # Done\n  archived/       # Historical reference\n```\n\nEach plan is a folder: `YYYY-MM-DD-plan-name/`\n\n## Plan Contents\n\n```\nYYYY-MM-DD-plan-name/\n  specs/              # Problem statements, requirements\n  proposal.md         # Why: justification, impact, risks\n  design.md           # How: architecture, flows, decisions\n  tasks.md            # What: checkboxes, owners, phases\n```\n\n### proposal.md\n\n```markdown\n# Proposal: [Plan Name]\n\n## Status\nDraft | Submitted | Approved | Rejected\n\n## Parent Plan\n[agent]/plans/[state]/[plan-name] (if child plan)\n\n## Problem\nWhat problem are we solving?\n\n## Proposed Solution\nHigh-level approach.\n\n## Impact\nWhat changes? What improves?\n\n## Cost / Effort\nTime, resources, dependencies.\n\n## Risks\nWhat could go wrong?\n\n## Decision\nApproved by [name] on [date] | Rejected because [reason]\n```\n\n### design.md\n\n```markdown\n# Design: [Plan Name]\n\n## Overview\nWhat are we building/doing?\n\n## Architecture / Approach\nHow does it work? Diagrams, flows, decisions.\n\n## Dependencies\nWhat do we need? Other plans, external services, other agents.\n\n## Constraints\nLimitations, rules, non-negotiables.\n\n## Open Questions\nThings still to be decided.\n```\n\n### tasks.md\n\n```markdown\n# Tasks: [Plan Name]\n\n## Summary\nBrief overview.\n\n## Tasks\n\n### Phase 1: [Name]\n- [x] Task description -> Owner\n  Completed YYYY-MM-DD. Notes.\n- [ ] Task description -> Owner\n  Details, acceptance criteria.\n- [ ] Delegate to [Agent]: [what] -> [Agent]\n  Child plan: [agent]/plans/[state]/[plan-name]\n```\n\n## Lifecycle\n\n1. **Draft** - Specs written, proposal drafted\n2. **Approved** - Proposal approved, design and tasks written\n3. **In Progress** - Execution started\n4. **Completed** - All tasks done\n5. **Archived** - Kept for reference\n\nMove the plan folder between state directories to change state.\n\n## When to Create a Plan\n\nCreate when: multi-agent coordination needed, significant effort, multiple phases, needs approval, or progress tracking desired.\n\nSkip for: quick tasks, simple lookups, routine operations.\n\n## Approval Authority\n\nDefine your own hierarchy. Typical pattern:\n\n- **Owner/CEO** approves strategic plans\n- **Lead agent** can approve plans aligned with established vision\n- **Sub-agents** submit proposals to their lead for approval\n\nDocument your approval chain in your workspace's `plans/README.md`.\n\n## Delegation\n\nWhen delegating work to another agent:\n\n1. Parent plan's `tasks.md` references the child plan path\n2. Child plan's `proposal.md` references the parent plan path\n\nExample in parent `tasks.md`:\n```markdown\n- [ ] Delegate to [Agent]: implement feature X\n  Child plan: [agent]/plans/in_progress/2026-02-20-feature-x\n```\n\nExample in child `proposal.md`:\n```markdown\n## Parent Plan\n[lead-agent]/plans/in_progress/2026-02-20-parent-plan\n```\n\n## On Session Start\n\n1. Check `plans/in_progress/` for active plans\n2. Check `plans/draft/` for plans awaiting action\n3. Continue where you left off\n\n## Granularity Tips\n\n- Not everything needs a plan. Use for significant, multi-step work.\n- A single agent working on a quick fix does not need a plan.\n- Plans shine when coordination, tracking, or approval is involved.\n- Keep plan documents concise. Verbose plans get ignored.\n","tags":{"latest":"1.0.0","multi-agent":"1.0.0","planning":"1.0.0","productivity":"1.0.0","project-management":"1.0.0","task-tracking":"1.0.0"},"stats":{"comments":0,"downloads":854,"installsAllTime":0,"installsCurrent":0,"stars":0,"versions":1},"createdAt":1771613770975,"updatedAt":1778491594064},"latestVersion":{"version":"1.0.0","createdAt":1771613770975,"changelog":"Initial release. Structured work tracking methodology with plan lifecycle (draft, approved, in_progress, completed, archived), folder conventions, proposal/design/tasks templates, hierarchical delegation, and approval authority for multi-agent teams.","license":null},"metadata":null,"owner":{"handle":"cramtek","userId":"s17fvxtdq58dnpwmnpmrejtk0n885ys7","displayName":"cramtek","image":"https://avatars.githubusercontent.com/u/7982236?v=4"},"moderation":null}