plan-author

Generate implementation plans with analysis, checklists, and testing strategy.

39|6|Updated Nov 7, 2025
One-click install
npx skills add https://github.com/ddobrin/gemini-plan-commands --skill plan-author
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-author
Source: https://github.com/ddobrin/gemini-plan-commands/tree/main/skills/plan-author
Command: npx skills add https://github.com/ddobrin/gemini-plan-commands --skill plan-author

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Designing and coordinating feature implementations is error-prone without a structured plan. This Skill acts as a Staff Engineer to generate comprehensive implementation plans that map discovery, strategy, and concrete steps, without changing the codebase.

Core Features & Use Cases

  • Thorough discovery and analysis before planning.
  • Strict plan template generation at plans/[feature-name].md.
  • Read-only planning mode; final plan is the artifact.
  • Ready-to-use for handoffs and reviews.
  • Supports testing strategy and success criteria.

Quick Start

Provide a feature request and I will generate a detailed implementation plan in plans/[feature-name].md using the strict template.

Frequently Asked Questions about plan-author

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

FAQPage Schema
How do I generate an implementation plan for a feature without writing code?

You can generate an implementation plan without writing code by providing a feature request to produce a detailed, read-only plans/[feature-name].md file using a strict template for handoffs and reviews.

What should a staff-level architecture roadmap document include for cross-team coordination?

A staff-level architecture roadmap document should include thorough discovery analysis, a step-by-step checklist, testing strategy, and success criteria to guide cross-team implementation and act as a living document.

How do I create a structured planning template for a new software feature?

You create a structured planning template by running a thorough discovery and analysis phase, then outputting an actionable markdown file with predefined sections for analysis, checklists, and step-by-step details.

Can I use this planning approach for cross-team work and architecture design?

Yes, you can use this planning approach for cross-team work and architecture design because it generates comprehensive plans mapping discovery, strategy, and concrete steps suitable for team coordination.

Does the generated plan document include a testing strategy and success criteria?

Yes, the generated plan document includes a testing strategy and success criteria. The output markdown file follows a strict template ensuring all implementation steps have defined validation and success metrics.

When should I avoid using a read-only implementation plan for software development?

You should avoid using a read-only implementation plan when your goal is to directly modify the codebase, because this approach operates strictly in a read-only planning mode where the final plan is the only artifact.