repo-planning-discipline

What problem does it solve?

Planning and governance for repository work are often inconsistent across tasks, leading to miscommunication, scope creep, and duplicated effort. This skill standardizes how plans are created, stored, and reviewed.

Core Features & Use Cases

• Promotes durable planning artifacts: committed exec-plans under docs/exec-plans/active/ and a session plan.md for ephemeral evaluation, plus a SQLite-backed SQL todos for tracking steps.
• Provides a clear Decision Flow and a Pre-Implementation Completeness Checklist to ensure scope, tests, validation, risks, and conflicts are addressed before implementation.
• Defines a repeatable workflow: PLAN → IMPLEMENT → REVIEW → COMMIT → WAIT, reducing back-and-forth and ensuring reproducible outcomes.

Quick Start

Create a new exec-plan for a non-trivial task and place it in docs/exec-plans/active/ with a clear filename, then draft a session plan.md for exploratory work and populate the SQL todos table during planning.