smithery/NickCrew

implementation-workflow

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

Installation

$ npx skills add smithery/NickCrew --skill implementation-workflow

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/NickCrew · top by installs.

npx skills add smithery/NickCrew

Browse all from smithery/NickCrew

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,564 B
  • docs SUMMARY.md 194 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

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