planner-handbook

Guide planner agents through spec.md authoring and revision workflows.

Updated Apr 30, 2026
One-click install
npx skills add https://github.com/zalman0813/gan-harness --skill planner-handbook
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planner-handbook
Source: https://github.com/zalman0813/gan-harness/tree/main/improver/setup-gan-harness-skills/iteration-1/eval-greenfield-cli/without_skill/outputs/.claude/skills/planner-handbook
Command: npx skills add https://github.com/zalman0813/gan-harness --skill planner-handbook

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill offers a comprehensive methodology handbook for the planner agent, guiding through various planning stages and enhancing efficiency in spec.md authoring.

Core Features & Use Cases

  • Grill Protocol: Extracts sufficient context for downstream agents to avoid repeated questions.
  • Archetype Templates: Provides templates for frontend, backend, library, CLI, data-pipeline, and hybrid archetypes.
  • ADR Three-Test Gate: Assists in identifying design choices worthy of an ADR (Architecture Decision Record).
  • Spec.md Authoring: Offers guidelines for writing clear, concise, and effective spec.md files.

Quick Start

Generate a new spec for a project using the planner-handbook skill by initiating a grill session with the planner agent.

Frequently Asked Questions about planner-handbook

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

FAQPage Schema
How do I write a spec.md for a software development project?

Writing a spec.md involves defining project scope, selecting archetypes, and applying architecture decision records. This handbook guides the planner agent through authoring clear, concise specifications to streamline your software development planning process.

What is the grill protocol in project planning?

The grill protocol in project planning is a context extraction process used by the planner agent. It ensures sufficient context is gathered upfront for downstream agents, preventing repeated questions during spec.md authoring.

When do I need an architecture decision record for my project methodology?

You need an architecture decision record (ADR) when your project methodology encounters specific design choices. The handbook applies an ADR three-test gate to identify which design choices warrant formal documentation during planning.

Can I use archetype templates for frontend, backend, and data-pipeline planning?

Yes, you can use archetype templates for frontend, backend, library, CLI, data-pipeline, and hybrid project planning. These templates provide structured starting points to streamline spec generation across diverse software development contexts.

How do I automate spec generation using a planner agent?

Automating spec generation with a planner agent involves initiating a grill session to extract context, selecting an archetype template, and applying ADR guidelines. This handbook provides the methodology to streamline the end-to-end authoring process.