# Build phased action plans

Teams often leave decisions without a clear path to execution. This skill turns a goal into phases, milestones, dependencies, risks, and checkpoints.

## Install

```bash
npx skillstore add bellabe/planning-action
```

## Metadata

- - Slug: bellabe-planning-action
- - Version: 1.0
- - Author: BellaBe
- - GitHub username: BellaBe
- - License: MIT
- - Repository: https://github.com/BellaBe/lean-os/tree/main/.claude/skills/action-planning
- - Ref: main
- - Supported tools: Claude, Codex, Claude Code
- - Risk level: safe
- - Quality score: 80
- - Quality tier: silver
- - Public page: https://skillstore.pages.dev/skills/bellabe-planning-action
- - Manifest: https://skillstore.pages.dev/api/skills/bellabe-planning-action/manifest

## Capabilities

- Restates a goal and its constraints before planning.
- Separates project scope from non-scope.
- Breaks execution into phases with milestones.
- Identifies dependencies that can block progress.
- Lists risks and contingency options.
- Keeps validation checkpoints at a high level.

## Use Cases

- Product launch roadmap: Create a phased rollout plan with milestones, dependencies, and launch risks.
- Implementation timeline: Turn an approved technical decision into an execution sequence for delivery teams.
- Operational change plan: Plan a process change with scope boundaries, checkpoints, and contingency actions.

## Prompt Templates

### Basic action plan

```
Create an action plan for this goal: [goal]. Include goal, scope, phases, dependencies, risks, and checkpoints.
```

### Timeline with constraints

```
Build a phased plan for [goal] under these constraints: [constraints]. Show milestones, dependencies, risks, and validation checkpoints.
```

### Rollout plan

```
Create a rollout plan for [initiative]. Define scope, non-scope, phases, milestones, dependencies, risks, and contingency options.
```

### Advanced execution sequence

```
Convert this decision into an execution plan: [decision]. Include assumptions, scope boundaries, phased work, dependencies, risks, owners by role, and checkpoints.
```

## Limitations

- It does not make the strategic decision for the user.
- It does not replace detailed project management software.
- It does not create repeatable operating procedures.
- It depends on the goal, constraints, and context supplied by the user.

## Best Practices

- Provide the goal, deadline, constraints, and known stakeholders.
- State what is already decided before asking for a plan.
- Review dependencies and risks before assigning owners or dates.

## Anti Patterns

- Using the skill for open-ended advice without a committed direction.
- Asking it to create detailed standard operating procedures.
- Providing a vague goal without constraints, scope, or success criteria.

## Security Audit

- - Safe to publish: true
- - Audited at: 2026-06-28T14:56:57.642\+00:00
- - Summary: The static analyzer flagged SKILL.md line 3 as a weak cryptographic algorithm, but the line is only a natural language description of planning use cases. No scripts, network behavior, filesystem access, external commands, prompt injection text, or data exfiltration intent were found in the reviewed skill file.

## Stats

- - Views: 193
- - Downloads: 5
- - Favorites: 0
- - Popularity score: 0