se-good-plan

Writes and reviews executable engineering plans with protected product authority and pre-phase rebase gates.

3|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/ceasarXuu/AstartesSkills --skill se-good-plan-ceasarxuu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: se-good-plan
Source: https://github.com/ceasarXuu/AstartesSkills/tree/main/skills/se-good-plan
Command: npx skills add https://github.com/ceasarXuu/AstartesSkills --skill se-good-plan-ceasarxuu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Engineering plans often drift from confirmed product intent, embed unconfirmed product decisions silently, and continue executing stale assumptions after implementation reality changes. This Skill enforces a single user-confirmed product authority, bounded decision audits, and evidence-driven plan rebasing so plans stay executable and aligned with what the user actually approved. ## Core Features & Use Cases - Single Product Authority: Reuses a canonical PRD's directly confirmed decisions when available, falling back to a protected decisions.md baseline only when no qualifying PRD exists, preventing duplicate sources of truth. - Executable Work Units: Every unit specifies a concrete change location, target object, action, resulting behavior, benefit, side effects, verification, and safe-stop boundary. - Phase Gates and Audits: Each material phase runs a Product Decision Delta audit after completion and a persisted Pre-Phase Plan Rebase Gate before starting, blocking execution until material plan changes receive explicit user approval. - Use Case: When asked to plan a multi-phase migration, the Skill creates docs/releases/<version>/<topic>/plan.md with an execution contract, references confirmed PRD decision IDs, and requires user approval before applying any material plan revision discovered during implementation. ## Quick Start Ask the agent to write an engineering plan for your next feature or refactor using the se-good-plan skill, providing the target release version and any existing PRD.

Frequently Asked Questions about se-good-plan

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

FAQPage Schema
How do I write an engineering implementation plan with an AI agent?

Invoke the skill with your topic and confirmed release version. It creates docs/releases/<version>/<topic>/plan.md containing a product authority reference, execution contract, design, and concrete work units with verification and rollback boundaries.

How does the skill handle unconfirmed product decisions in a plan?

Unconfirmed material product choices stay in plan.md under Pending Product Decisions as deferred, provisional, or blocked. They never enter the authority baseline without direct user confirmation, and provisional or conflicting decisions block dependent work.

Can the skill review an existing engineering plan?

Yes. It leads with findings, checking for duplicated product authority, agent-authored decisions, missing execution contracts, stale remaining work, missing rebase gates, vague work units, and material plan changes applied without user approval.

What is the Pre-Phase Plan Rebase Gate?

It is a persisted checkpoint inside each material phase of plan.md. Before the phase starts, completed implementation is compared against all remaining planned work; material differences require a recorded plan delta and explicit user approval before execution continues.

When should I not use this planning skill?

Avoid it for trivial single-step changes where a formal plan artifact adds no value. The full structure with authority baselines, phases, and gates is designed for multi-step engineering work with material product decisions.