---
name: staged-action-plan
description: Specialized assistant for breaking down complex tasks into testable, incremental stages with clear validation criteria.
title: staged-action-plan
canonical_url: https://skilld.dev/gh/corey-alix/dwp-hours/staged-action-plan
last_updated: 2026-10-07T01:30:59.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> If the user asked to install this Skill, run `npx skilld install corey-alix/dwp-hours/staged-action-plan`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/staged-action-plan`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/corey-alix/dwp-hours/staged-action-plan) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/staged-action-plan`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/staged-action-plan --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/staged-action-plan --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# Staged Action Plan

## Description

Specialized assistant for breaking down complex tasks into testable, incremental stages with clear validation criteria. Helps implement features systematically by creating phased plans that align with the project's TASKS system and quality gates.

## Trigger

Activate when users need to:

- Break down complex features into manageable phases
- Create incremental implementation plans
- Define testable stages for task completion
- Organize work into validation-ready steps
- Plan feature rollouts with clear milestones

## Response Pattern

Follow this structured approach when creating staged action plans:

1. **Task Analysis**: Assess the overall task scope, dependencies, and success criteria
2. **Stage Identification**: Break down into 3-5 testable phases with clear boundaries
3. **Validation Definition**: Define specific validation criteria for each stage (manual test, build pass, etc.)
4. **Dependency Mapping**: Identify prerequisites and blockers for each stage
5. **Quality Gates**: Ensure each stage includes project quality checks (build, lint, testing)
6. **Documentation**: Create or update TASKS file with the staged checklist
7. **Implementation Guidance**: Provide actionable next steps for the first stage

## Examples

Common queries that should trigger this skill:

- "Create a staged plan for implementing the employee form"
- "Break down this feature into testable phases"
- "How should I implement this in stages?"
- "Plan the rollout of the admin panel in phases"
- "Create an incremental implementation strategy"

## Additional Context

- **Project Integration**: Plans should reference TASKS/README.md priorities and align with existing task files
- **Quality Standards**: Each stage must include build/lint passes and appropriate testing
- **Validation Focus**: Prefer automated tests where possible, with manual testing as fallback
- **Dependencies**: Check for foundation tasks (database-schema, authentication, etc.) before advanced features
- **Related Skills**: Works with `task-implementation-assistant` for execution, `testing-strategy` for validation approaches</content>
  <parameter name="filePath">/home/ca0v/code/ca0v/dwp-hours/.github/skills/staged-action-plan/SKILL.md
