planning

Manage project scope, constraints, and success criteria with a decision ledger.

2|Updated Feb 18, 2021
One-click install
npx skills add https://github.com/jinyongp/dotfiles --skill planning-jinyongp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planning
Source: https://github.com/jinyongp/dotfiles/tree/main/agents/skills/planning
Command: npx skills add https://github.com/jinyongp/dotfiles --skill planning-jinyongp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves ambiguity and prevents project drift by enforcing a structured, evidence-based approach to planning, design, and complex implementation tasks.

Core Features & Use Cases

  • Decision Ledger: Maintains a clear, persistent record of open decisions, constraints, and success criteria within the conversation.
  • Guardrail Enforcement: Validates assumptions and identifies tradeoffs before execution to prevent avoidable complexity and security risks.
  • Use Case: When starting a complex refactor, use this skill to define success criteria, surface technical tradeoffs, and ensure all dependent decisions are reconciled before writing any code.

Quick Start

Initiate a planning session by asking the agent to help define the scope and success criteria for your upcoming project task.

Frequently Asked Questions about planning

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

FAQPage Schema
What is structured project planning for complex software architecture?

Structured project planning resolves ambiguity by enforcing evidence-based decision-making, managing scope, constraints, and success criteria for complex development tasks. It prevents project drift through rigorous trade-off analysis and validation.

How do I define success criteria for a complex refactor?

Define success criteria for a complex refactor by initiating a planning session to scope the task, surface technical tradeoffs, and reconcile dependent decisions before writing any code. This ensures all constraints are validated.

How do I track technical decisions during ambiguous development tasks?

Track technical decisions during ambiguous development tasks by maintaining a persistent decision ledger within the conversation. This records open decisions, constraints, and success criteria to enforce evidence-based recommendation standards.

When do I need rigorous trade-off analysis for project management?

Rigorous trade-off analysis is needed for non-trivial development tasks requiring scope management and constraint validation. It identifies avoidable complexity and security risks by validating assumptions before execution begins.

Does guardrail enforcement prevent security risks during architecture planning?

Guardrail enforcement prevents security risks during architecture planning by validating assumptions and identifying tradeoffs before execution. This structured approach avoids preventable complexity in ambiguous project workflows.

What are the limitations of using structured decision-making protocols?

Structured decision-making protocols require strict adherence to explicit decision-tracking and evidence-based standards, making them less suitable for trivial tasks or rapid prototyping where lightweight architectural planning suffices.