Name: ETKM Project Planning Protocol
Author: easttxkravmaga

ETKM Project Planning Protocol

Project planning protocol for East Texas Krav Maga. Load this skill before any new project, feature build, or multi-session initiative. Enforces the REBB protocol: start at the finish line, work backwards to today, map every dependency, identify every gap, verify every tool assignment, then write the build sequence. The governing principle: never ask "what should we build?" — ask "what does working look like, and what has to be true for that to exist?" Trigger before any planning session, any new project kickoff, or any time a build session is about to start without a plan.

easttxkravmaga0 スター2026/03/29

職業
カテゴリ: プロジェクト管理

Version: 1.0 Last Updated: 2026-03-21

The most expensive problems are discovered after building starts. This skill finds them before.

THE GOVERNING PRINCIPLE

Start at the finish line. Work backwards to today.

Never ask "what should we build?" Ask "what does working look like — and what has to be true for that to exist?"

THE 5-STEP PROTOCOL

Step 1 — Define the End State

Write what success looks like in precise, specific terms before anything else. No building until this is written and confirmed.

Step 2 — Map Every Dependency

Work backwards from the end state. For each dependency ask: what has to be true for this to exist? Keep going until you hit ground level.

Step 3 — Identify All Gaps

List every gap with owner, path, and estimated time. If any gap has no clear owner — stop and resolve before building.

Version: 1.0 Last Updated: 2026-03-21

The most expensive problems are discovered after building starts. This skill finds them before.

THE GOVERNING PRINCIPLE

Start at the finish line. Work backwards to today.

Never ask "what should we build?" Ask "what does working look like — and what has to be true for that to exist?"

THE 5-STEP PROTOCOL

Step 1 — Define the End State

Write what success looks like in precise, specific terms before anything else. No building until this is written and confirmed.

Step 2 — Map Every Dependency

Work backwards from the end state. For each dependency ask: what has to be true for this to exist? Keep going until you hit ground level.

Step 3 — Identify All Gaps

List every gap with owner, path, and estimated time. If any gap has no clear owner — stop and resolve before building.

Session Type	Contains	Does NOT contain
Planning	REBB protocol, dependency mapping	Any actual building
Content	Writing, copy, PDF drafts	Code, deployment
Build	Code writing, skill development	Deployment, content
Deployment	Production deployment only	New features, content
Review	QC, testing, validation	New building

ETKM Project Planning Protocol

THE GOVERNING PRINCIPLE

THE 5-STEP PROTOCOL

Step 1 — Define the End State

Step 2 — Map Every Dependency

Step 3 — Identify All Gaps

ETKM Project Planning Protocol

THE GOVERNING PRINCIPLE

THE 5-STEP PROTOCOL

Step 1 — Define the End State

Step 2 — Map Every Dependency

Step 3 — Identify All Gaps

Step 4 — Verify Tool Assignments

Step 5 — Write the Build Sequence

THE IRON RULE

SESSION SCOPE RULES

THE PLANNING DOCUMENT

Things Mac

Trello

Production Scheduling

Jira Integration

Production Scheduling

Cost Aware Llm Pipeline