plan-author

Author and validate project plans with measurable success criteria in YAML.

2|Updated Jul 13, 2025
One-click install
npx skills add https://github.com/krzemienski/shannon --skill plan-author-krzemienski
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-author
Source: https://github.com/krzemienski/shannon/tree/main/skills/plan-author
Command: npx skills add https://github.com/krzemienski/shannon --skill plan-author-krzemienski

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps users author and validate detailed project plans, ensuring that each phase is scoped, measurable, and verifiable.

Core Features & Use Cases

  • Plan Authoring: Author plans using a structured format, with each phase defined with measurable success criteria.
  • Validation: Automatically validate plans against the specified success criteria.
  • Use Case: Plan a new feature implementation, ensuring that each phase of the development process is well-defined and has clear outcomes.

Quick Start

/shannon:plan-author

Frequently Asked Questions about plan-author

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

FAQPage Schema
How do I create a project plan with measurable success criteria for each phase?

You can author a project plan with measurable success criteria using a structured YAML-based planning format. The Skill validates each defined phase to ensure it is scoped, measurable, and verifiable for software development or strategic planning workflows.

What is the best way to validate project phases against specific success criteria?

The best way to validate project phases is by applying automated plan validation against the specified success criteria. This mechanism checks your YAML-based plan structure to verify that every phase has clear, measurable outcomes before development begins.

How do I structure a YAML project plan for feature implementation?

You structure a YAML project plan for feature implementation by defining each phase with explicit, measurable success criteria. This format requires domain expertise and context from earlier planning stages to ensure proper phase management and scoping.

Can I use this for strategic planning workflows or is it limited to software development?

You can use this plan validation approach for both strategic planning workflows and software development. The YAML-based planning format applies to project management broadly, ensuring phases are well-defined with clear, verifiable outcomes across domains.

Do I need prior planning context to author and validate a detailed project plan?

Yes, you need prior planning context and domain expertise to author a detailed project plan. The plan authoring process builds upon context from previous planning stages to accurately define and validate measurable success criteria for each phase.

Why does project plan validation fail when phases lack measurable outcomes?

Project plan validation fails when phases lack measurable outcomes because the validation mechanism specifically checks for defined success criteria. Without clear, verifiable metrics in the YAML format, the system cannot confirm that a phase is properly scoped.