plan-authoring

Generate structured implementation plans with architecture decisions, data models, and API contracts.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/patrickrmoore/sdd-test --skill plan-authoring-patrickrmoore
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-authoring
Source: https://github.com/patrickrmoore/sdd-test/tree/main/.github/skills/plan-authoring
Command: npx skills add https://github.com/patrickrmoore/sdd-test --skill plan-authoring-patrickrmoore

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan Authoring provides a structured approach to generate implementation plans that align technical context, architecture decisions, data models, API contracts, and project instructions, reducing ambiguity and misalignment across teams.

Core Features & Use Cases

  • Create decision-rich implementation plans that trace architecture decisions, data models, and API contracts to actionable tasks.
  • Align project instructions with technical context to ensure consistent execution and governance.
  • Use during feature design, technology selection, data-structure definition, or when resolving NEEDS CLARIFICATION markers in plans.

Quick Start

Provide the feature goal and context, then run Plan Authoring to generate a complete implementation plan.

Frequently Asked Questions about plan-authoring

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

FAQPage Schema
How do I create an implementation plan that ties architecture decisions to actionable tasks?

A structured implementation plan aligns technical context, architecture decisions, data models, and API contracts with actionable tasks. This ensures traceable decisions and consistent execution across teams.

What is a structured implementation plan in software architecture?

A structured implementation plan formalizes feature design, technology selections, and data structure definitions into a checkable format. It aligns project instructions with technical context to ensure consistent execution and governance.

How do I resolve NEEDS CLARIFICATION markers across project plans?

NEEDS CLARIFICATION markers are resolved by applying structured plan authorship during feature design or data structure definition. This process ties technical context and architecture decisions to actionable work, clarifying ambiguities.

Can I use plan authoring to define API contracts and data models together?

Yes, plan authoring defines data structures and API contracts within the same implementation plan. It traces these definitions alongside architecture decisions to ensure alignment with project instructions.

Does plan authoring work for technology selection and feature design?

Yes, plan authoring applies directly during technology selection and feature design. It generates decision-rich implementation plans that check project-instruction alignment and provide traceable technical context.

What is the best way to ensure project instructions align with technical context?

The best way to align project instructions with technical context is using a formal, checkable implementation plan. Plan authorship traces architecture decisions and data models to actionable tasks, ensuring consistent execution and governance.