task-planning | spec-kit | ClaudePluginHub

Skill

Community

task-planning

11

Description

Generate dependency-ordered implementation tasks from specifications and plans. Create actionable, phased task breakdowns for systematic implementation. Triggers: task planning, task generation, dependency ordering, implementation planning, phased breakdown, parallel tasks, task dependencies Use when: converting specifications to tasks, planning implementation order, identifying parallel execution opportunities, breaking down complex features DO NOT use when: writing specifications - use spec-writing. DO NOT use when: executing tasks - use implementation-executor agent. Produces tasks.md with phased, dependency-ordered implementation tasks.

Install

1

Add the repository(one-time)

$

/plugin marketplace add athola/claude-night-market

2

Install the plugin

$

/plugin install sanctum@claude-night-market

Tool Access

This skill inherits all available tools. When active, it can use any tool Claude has access to.

Supporting Assets

View in Repository

modules/dependency-patterns.md

modules/phase-structure.md

Skill Content

Task Planning

Overview

Transforms specifications and implementation plans into actionable, dependency-ordered tasks. Creates phased breakdowns that guide systematic implementation.

When to Use

Converting specifications to implementation tasks
Planning feature implementation order
Identifying parallel execution opportunities
Breaking down complex features into phases

Task Phases

Tasks follow a 5-phase structure from setup through polish:

Phase 0: Setup - Project initialization, dependencies, configuration
Phase 1: Foundation - Data models, interfaces, test infrastructure
Phase 2: Core Implementation - Business logic, APIs, services
Phase 3: Integration - External services, middleware, logging
Phase 4: Polish - Optimization, documentation, final testing

For detailed phase definitions, selection guidelines, and anti-patterns, see modules/phase-structure.md.

Task Format

Each task includes:

ID: Unique identifier (TASK-001)
Description: Clear action statement
Phase: Which phase it belongs to
Dependencies: Tasks that must complete first
Parallel Marker: [P] if can run concurrently
Files: Affected file paths
Criteria: How to verify completion

Dependency Rules

Dependencies define execution order and identify parallelization opportunities:

Sequential Tasks: Execute in strict order when dependencies exist
Parallel Tasks [P]: Can run concurrently when no conflicts exist
File Coordination: Tasks affecting same files must run sequentially

For fan-out/fan-in patterns, task ID conventions, and validation rules, see modules/dependency-patterns.md.

Example Task Entry

## Phase 2: Core Implementation

### TASK-007 - Implement user authentication service [P]
**Dependencies**: TASK-003, TASK-004
**Files**: src/services/auth.ts, src/types/user.ts
**Criteria**: All auth tests pass, tokens are valid JWT

Quality Checklist

All requirements mapped to tasks
Dependencies are explicit
Parallel opportunities identified
Tasks are right-sized (not too large/small)
Each task has clear completion criteria

Related Skills

spec-writing: Creating source specifications
speckit-orchestrator: Workflow coordination

Links

GitHub Stats

2 forks

Similar Skills

Command Development

This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.

47.1k

Agent Development

This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.

47.1k

Hook Development

This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.

47.1k