skills.rest
davidmatousek
davidmatousekCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

~aod-plan

Automate Plan-stage governance across spec.md, plan.md, and tasks.md with gate-based approvals.

86|21|Updated Mar 21, 2026
Search Tags:#orchestration#governance#spec#tasks#project-plan#plan-stage
One-click install
npx skills add https://github.com/davidmatousek/tachi --skill aod-plan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ~aod-plan
Source: https://github.com/davidmatousek/tachi/tree/main/.claude/skills/~aod-plan
Command: npx skills add https://github.com/davidmatousek/tachi --skill aod-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates end-to-end Plan-stage governance by coordinating spec.md, plan.md, and tasks.md with gate-based approvals across the feature lifecycle.

Core Features & Use Cases

  • Orchestrates the full Plan stage by coordinating spec.md, plan.md, and tasks.md with governance gates.
  • Automatically advances through steps on APPROVED and stops on CHANGES_REQUESTED or BLOCKED.
  • Validates artifact existence and sign-offs, re-reading statuses after each sub-step to decide the next action.
  • Enforces PRD input requirements and handles edge cases in feature planning workflows.

Quick Start

Provide a feature's PRD and run /aod.plan to initiate the orchestration across spec, plan, and tasks.

Frequently Asked Questions about ~aod-plan

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

FAQPage Schema
How do I automate feature planning governance across spec, plan, and tasks documents?▼

Gate-based plan governance coordinates spec.md, plan.md, and tasks.md by validating artifact existence and sign-offs. It advances automatically when approvals are granted and halts on changes requested or blocked statuses.

What is needed to start automated orchestration for a feature plan?▼

Automated plan orchestration requires a feature PRD as input. Providing the PRD and running the initiation command starts coordinating spec, plan, and tasks documents through their governance gates.

How does governance orchestration handle rejections or blocked statuses?▼

Plan governance orchestration stops progression upon changes requested or blocked statuses. It resumes after rejections are addressed by re-reading artifact statuses after each sub-step to decide the next routing action.

Does plan governance enforce multi-role sign-offs for feature planning?▼

Plan governance enforces multi-role sign-offs alongside PRD input requirements. It validates these artifact statuses before routing to the next orchestration step in the feature planning lifecycle.

Can I use this orchestration for end-to-end feature lifecycle workflows?▼

This orchestration manages the end-to-end plan stage for feature lifecycle workflows. It handles edge cases in feature planning by validating artifacts and coordinating approvals across spec, plan, and tasks files.

Related Skills

Explore More Product & Management Skills→
compnew2006compnew2006
63

speckit.tasks

Convert plan.md and spec.md into a dependency-ordered tasks.md.

Community
Advanced
gvinokurgvinokur

implementer

Execute approved implementation plans into validated code with tests, lint, and builds.

Community
Advanced
shaul1991shaul1991

dashboard

Scan project roots to generate lifecycle status dashboards with ALM governance.

Community
Intermediate
ahgraberahgraber
5

spec-kit

Route requests to spec-kit sub-skills and enforce artifact-order gates.

Community
Intermediate