home / skills / nickcrew / claude-cortex / implementation-workflow

implementation-workflow skill

safe

This skill converts PRDs or feature specs into actionable implementation workflows with task breakdowns, dependencies, and validation gates.

npx playbooks add skill nickcrew/claude-cortex --skill implementation-workflow

Review the files below or copy the command above to add this skill to your agents.

Files (2)

SKILL.md

1.2 KB

---
name: implementation-workflow
description: Use when turning PRDs or feature specs into actionable implementation workflows - provides structured task decomposition, dependency mapping, and validation gates.
---

# Implementation Workflow

## Overview
Create structured implementation workflows from PRDs or feature requirements. Emphasize clear task breakdowns, dependencies, and validation checkpoints.

## When to Use
- Translating a PRD or feature spec into tasks
- Planning multi-domain implementation work
- Defining validation gates and dependencies

Avoid when:
- The task is a small, obvious change
- You already have a complete plan

## Quick Reference

| Task | Load reference |
| --- | --- |
| Workflow generation | `skills/implementation-workflow/references/workflow.md` |

## Workflow
1. Read the PRD/spec and identify core requirements.
2. Load the workflow reference for structure and patterns.
3. Decompose into workstreams with dependencies.
4. Add validation steps and risk mitigation.
5. Deliver the workflow and next actions.

## Output
- Structured workflow with tasks and dependencies
- Validation checklist and risks

## Common Mistakes
- Skipping dependency mapping
- Mixing execution steps with brainstorming
- Omitting validation gates

Overview

This skill converts PRDs or feature specs into actionable implementation workflows with clear task decomposition, dependency mapping, and validation gates. It produces a structured plan that teams can execute, track, and hand off. The output highlights risks, validation checkpoints, and next actions for rapid alignment.

How this skill works

I read the PRD or feature spec to extract core requirements and success criteria, then decompose the work into discrete tasks and workstreams. Dependencies and sequencing are mapped so parallel and blocking work are visible. Validation gates and risk mitigations are added to ensure each milestone is testable and releasable.

When to use it

Turning a PRD or feature spec into an executable plan
Coordinating multi-domain work across engineering, QA, and product
Defining release checkpoints, validation gates, and rollout criteria
Planning integrations or features with complex dependencies
Preparing handoff-ready backlog items for sprint planning

Best practices

Start by extracting clear success criteria and acceptance tests from the spec
Group tasks into workstreams (frontend, backend, infra, QA, docs) and map inter-workstream dependencies
Define explicit validation gates tied to measurable checks or test cases
Flag risks and add mitigation tasks alongside primary work items
Keep tasks actionable and time-boxed; avoid mixing brainstorming with execution steps

Example use cases

Converting a new feature PRD into a prioritized sprint backlog with dependencies
Planning a cross-team integration that requires feature flags, schema changes, and migration steps
Creating a release plan with validation gates for canary, beta, and full rollout
Preparing acceptance criteria and test checkpoints for a compliance-related feature

FAQ

How granular should tasks be?

Break tasks to the level where a single owner can complete them within a sprint or a few days; include sub-tasks for complex activities like migrations or end-to-end tests.

How are validation gates defined?

Validation gates are defined as measurable checks or tests tied to success criteria, such as unit/integration test pass rates, performance thresholds, or stakeholder sign-offs.