skills.rest
amoutiers
amoutiersCOMMUNITY
Explore all skills by this author →
GitHub

plan

Generate an implementation plan from a clarified spec via /maxi:writing-plans.

1|Updated May 28, 2026
Search Tags:#architecture#implementation#adr#constitution#spec#plan
One-click install
npx skills add https://github.com/amoutiers/maxi-superpowers --skill plan-amoutiers
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/amoutiers/maxi-superpowers/tree/main/skills/plan
Command: npx skills add https://github.com/amoutiers/maxi-superpowers --skill plan-amoutiers

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translating a clarified feature spec into a concrete, executable implementation plan is error-prone and time-consuming. This Skill automates the planning phase by coordinating constitution checks, delegating to /maxi:writing-plans, and producing structured plan artifacts that map to the original spec.

Core Features & Use Cases

  • Delegates planning to /maxi:writing-plans to produce a complete implementation plan aligned with the spec.
  • Performs pre-flight constitution validation and surfaces violations before planning proceeds.
  • Generates documentation artifacts under docs/maxi/specs/NNNN-slug/ (plan.md, and related outputs) and can trigger ADR creation when architectural decisions are captured.

Quick Start

Run /maxi:plan to generate an implementation plan from the current clarified spec and constitution.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I generate an implementation plan from a clarified spec?▼

To generate an implementation plan from a clarified spec, run the planning command to delegate drafting, validate constitution checks, and output a structured plan.md artifact mapped to the original spec.

What is the process for translating software architecture specs into executable plans?▼

Translating software architecture specs into executable plans involves validating the spec status against a constitution, delegating to plan writing logic, and updating the spec frontmatter to a planned state.

Do I need a clarified spec before starting the implementation planning phase?▼

Yes, you need a clarified spec before planning proceeds. The process operates only after the spec status is clarified and pre-flight constitution validations pass to ensure alignment.

Can I capture architectural decisions and trigger ADR creation during planning?▼

Yes, you can capture architectural decisions and trigger ADR creation during planning. The process generates documentation artifacts under the spec directory and can initiate ADR creation for architectural choices.

What happens if my spec violates pre-flight constitution checks before planning?▼

If your spec violates pre-flight constitution checks, the implementation planning process surfaces those violations and halts. Planning only proceeds once the spec passes all constitution validations.

Related Skills

Explore More Software Engineering Skills→
yoshisadayoshisada

kiln-analyze

Analyze spec.md, plan.md, and tasks.md for cross-artifact inconsistencies.

Community
Advanced
spaarke-devspaarke-dev
1

project-init

Generate standardized project artifacts from a design specification.

Community
Basic
stark-ai-destark-ai-de
4

codex-spec-interviewer

Interview users to capture requirements and draft Codex-executable implementation specs.

Official
Advanced
Jia-Hong-PengJia-Hong-Peng

speckit-plan

Generate structured implementation plans from spec.md files using spec-kit workflows.

Community
Intermediate