sd-objective-plan

Generates milestone-based plans with dependencies, risks, and decision points from accepted goals.

Updated Jun 26, 2026
One-click install
npx skills add https://github.com/platypeeps/sd-ai-command-pack --skill sd-objective-plan-platypeeps
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sd-objective-plan
Source: https://github.com/platypeeps/sd-ai-command-pack/tree/main/contrib/sd-objective-plan
Command: npx skills add https://github.com/platypeeps/sd-ai-command-pack --skill sd-objective-plan-platypeeps

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Turning an accepted goal into an actionable plan often produces vague task lists with invented owners, dates, and estimates. This Skill converts one accepted outcome into a bounded, evidence-aware plan with observable milestones, explicit assumptions, and only actions that fit current authority. ## Core Features & Use Cases - Outcome-Based Milestones: Works backward from the desired end state into milestones, each with a changed-state description, completion signal, prerequisites, and acceptance evidence. - Assumption and Risk Auditing: Separates verified constraints and accepted commitments from assumptions and proposals, and maps risks with triggers, mitigations, and escalation points. - Dependency and Decision Mapping: Builds a dependency graph, surfaces cycles and missing prerequisites, and marks decision points with required evidence and authorized decision-makers. - Use Case: After leadership accepts a decision to enter a new market, use this Skill to produce a phased plan with milestones, unassigned owners clearly labeled, risks with leading indicators, and the smallest next action executable under current authority. ## Quick Start Use sd-objective-plan with goal="launch the partner pilot program by Q3" and constraints="budget capped at 50k, two engineers available" to produce a milestone plan with risks and next actions.

Frequently Asked Questions about sd-objective-plan

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

FAQPage Schema
How do I turn an accepted decision into an actionable project plan?▼

Provide the accepted outcome via the goal argument plus any constraints, horizon, and resources. The skill works backward into outcome-based milestones with completion signals, dependencies, risks, and immediate next actions that fit current authority.

What is the difference between sd-objective-plan and sd-decide?▼

sd-decide resolves which alternative to choose when the decision is still open, while sd-objective-plan starts after a direction is accepted and structures how to reach it. If alternatives are unresolved, planning stops and routes to sd-decide.

Can sd-objective-plan create tasks or calendar entries automatically?▼

No. The skill is strictly read-only and never creates tasks, files, calendar events, messages, purchases, or commitments. Any proposed external write is marked not run and requires a separate explicit authorized request.

When should I not use sd-objective-plan for planning?▼

Do not use it when the goal is not yet accepted or success criteria are unresolved, or when the request is software implementation inside a repository with its own development workflow. Those cases route to sd-decide or the local workflow.

How does the skill handle missing owners, dates, or estimates?▼

Missing commitments are labeled unknown, unassigned, or unscheduled rather than invented. Assumptions are made explicit with their basis, impact if wrong, and the smallest validation step.