plan

Generate validated implementation plans with inline organizational context.

13|1|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/unblocked/cookbook --skill plan-unblocked
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/unblocked/cookbook/tree/main/recipes/plan
Command: npx skills add https://github.com/unblocked/cookbook --skill plan-unblocked

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Context-aware planning helps teams generate a validated, inline-context implementation plan without writing code, improving handoffs and alignment.

Core Features & Use Cases

  • Hydrate with organizational context to embed decisions, patterns, and templates directly into the plan.
  • Validate the plan against team conventions and known constraints, ensuring actionable milestones and ownership.
  • Use cases include planning changes for new features, migrations, or process improvements, then handing off to teammates or future work.

Quick Start

Copy this skill into your .claude/skills folder and run the planner with your task prompt.

Frequently Asked Questions about plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create an implementation-ready plan for team handoffs?

Create a validated, self-contained plan by gathering organizational context and embedding decisions, patterns, and templates directly inline. This ensures your implementation plan is actionable with clear milestones and ownership for teammate handoffs.

What is context-aware planning for team workflows?

Context-aware planning hydrates a plan with organizational context, embedding team conventions and constraints directly into the document. This validates the plan against known constraints, improving team alignment without writing actual code.

How do I validate a migration plan against team conventions?

Validate a migration plan by gathering organizational context and checking the output against team conventions and known constraints. The plan template ensures inline citations and validation, guaranteeing actionable milestones and clear ownership.

Do I need templates to produce an inline-context implementation plan?

Yes, the planning process requires pattern templates such as the references plan-template to ensure inline context and citations. These templates structure the validated, self-contained plan output for future work across multiple domains.

Can I use this for planning process improvements without writing code?

Yes, you can plan changes for new features, migrations, or process improvements without writing code. The planner generates an implementation-ready plan with inline context, specifically designed to improve handoffs and team alignment.

What's the best way to document decisions for future work across multiple domains?

Document decisions by gathering organizational context and producing a validated plan with inline citations. Using a structured template ensures the self-contained plan captures all necessary patterns and constraints for cross-domain future work.