skills.rest
FPXszk
FPXszkCOMMUNITY
Explore all skills by this author →
GitHub

repo-planning-discipline

Standardize repository planning with exec-plans, session plans, and SQL todos.

1|Updated Apr 3, 2026
Search Tags:#workflow#planning#documentation#governance#task-management#session-plan#exec-plans
One-click install
npx skills add https://github.com/FPXszk/Oh-MY-TradingView --skill repo-planning-discipline
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: repo-planning-discipline
Source: https://github.com/FPXszk/Oh-MY-TradingView/tree/main/.agents/skills/repo-planning-discipline
Command: npx skills add https://github.com/FPXszk/Oh-MY-TradingView --skill repo-planning-discipline

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about repo-planning-discipline

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

FAQPage Schema
How do I prevent scope creep during repository task planning?▼

Prevent scope creep during repository task planning by enforcing a disciplined workflow that requires committed exec-plans and a pre-implementation checklist addressing scope, risks, and tests before writing any code.

What is the best way to standardize repository planning artifacts for non-trivial tasks?▼

Standardize repository planning artifacts by placing durable execution plans in docs/exec-plans/active/, using a session plan.md for ephemeral evaluation, and tracking implementation steps with a SQLite-backed SQL todos table.

How does the PLAN to COMMIT workflow improve task management governance?▼

The PLAN to COMMIT workflow improves task management governance by defining a repeatable sequence of PLAN, IMPLEMENT, REVIEW, COMMIT, and WAIT, which reduces back-and-forth and ensures reproducible outcomes for repository work.

When do I need to create an exec-plan versus a session plan for repository work?▼

Create a durable exec-plan under docs/exec-plans/active/ for non-trivial tasks, while drafting a session plan.md for exploratory work to maintain ephemeral evaluation without cluttering the permanent governance documentation.

What should be verified on the pre-implementation completeness checklist before coding?▼

Before coding, the pre-implementation completeness checklist must verify that scope, tests, validation, risks, and conflicts are fully addressed to prevent miscommunication and duplicated effort during the implementation phase.

Related Skills

Explore More Product & Management Skills→
Alexander-TyagunovAlexander-Tyagunov
12

almanac

Initialize Magician workspaces with directory structure, CLAUDE.md, and permissions allowlist.

Community
Advanced
costrict-plugins-repocostrict-plugins-repo

executing-plans

Execute written implementation plans with critical review checkpoints.

Official
Advanced
nakane1chomenakane1chome

dev-record

Capture per-session agent activity into JSON audit artifacts via hooks.

Community
Advanced
mikersaysmikersays

plan-init

Create a project planning directory with YAML frontmatter and markdown files.

Community
Basic