OpenSkillIndex← back to search
claude-code

Claude-code-blueprint sprint-plan

MUST use when user describes a multi-step feature to build, says 'let's build', 'new project', 'let's implement', or when a task clearly requires more than 3 steps and no plan exists yet. Do NOT trigger for simple additions like adding a comment, renaming a variable, or single-file changes.

install
source · Clone the upstream repo
git clone https://github.com/faizkhairi/claude-code-blueprint
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/faizkhairi/claude-code-blueprint "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/sprint-plan" ~/.claude/skills/faizkhairi-claude-code-blueprint-sprint-plan && rm -rf "$T"
manifest: skills/sprint-plan/SKILL.md
source content

Create a sprint plan for: $ARGUMENTS

  1. Analyze the requirement: Understand scope, constraints, dependencies
  2. Check existing code: Search codebase for related implementations that can be reused
  3. Break into tasks:
    • Each task should be independently deliverable
    • Include file paths that will be modified or created
    • Estimate size: S (< 1hr), M (1-4hr), L (4-8hr), XL (> 1 day)
  4. Sequence tasks: Identify dependencies, mark blocking tasks, find parallelizable work
  5. Identify risks: What could go wrong? What needs clarification?
  6. Output format:

Sprint Plan: [Feature Name]

Tasks

#TaskSizeDepends OnFiles
1...S-path/to/file

Risks

  • [Risk description and mitigation]

Definition of Done

  • All tasks completed
  • Tests written and passing
  • Code reviewed
  • Documentation updated
  • No security vulnerabilities introduced