writing-backlog-plans

Generate Backlog.md-compliant plans and hierarchical subtask trees under a parent task.

2|Updated Apr 22, 2026
One-click install
npx skills add https://github.com/jimmi-joensson/OpenWhisper --skill writing-backlog-plans
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-backlog-plans
Source: https://github.com/jimmi-joensson/OpenWhisper/tree/main/.claude/skills/writing-backlog-plans
Command: npx skills add https://github.com/jimmi-joensson/OpenWhisper --skill writing-backlog-plans

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Writing and coordinating implementation plans for projects that use Backlog.md can be error-prone and fragmented. This skill automates the creation of design/spec artifacts and a structured Backlog.md subtask tree under a chosen parent task, ensuring a single source of truth for plans, specs, and progress.

Core Features & Use Cases

  • Generate backlog/docs/plans markdown under backlog/docs/plans for the plan and create a Backlog.md subtask tree under the parent task.
  • Enforce a consistent planning workflow: one plan task per plan task, explicit acceptance criteria, status tracking, and a reviewer check.
  • Attach design artifacts and plan artifacts to the parent task via backlog docs references for traceability and easy review.

Quick Start

Provide the parent task identifier and scope to generate a complete backlog-driven implementation plan with a plan markdown and corresponding Backlog.md subtasks.

Frequently Asked Questions about writing-backlog-plans

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Backlog.md implementation plans and subtask creation?

Backlog.md subtask creation maps one plan task to one subtask, enforcing explicit acceptance criteria, status tracking, and reviewer checks. This ensures a single source of truth for your implementation progress and design artifacts.

Does this backlog planning workflow require specific repository configuration?

Yes, this backlog planning workflow applies when your repository has backlog configuration or CLAUDE.md references the backlog CLI. This environment setup is required to produce the compliant plan docs and subtask hierarchy.

What's the best way to structure Backlog.md tasks for design traceability?

Backlog.md task-to-subtask mapping enforces consistent plan structure by generating one subtask per plan task. Design artifacts are attached to the parent task through backlog docs references, maintaining traceability and enabling easy review.

How do I enforce acceptance criteria and reviewer checks in Backlog.md plans?

Enforcing acceptance criteria and reviewer checks in Backlog.md plans is achieved through the structured planning workflow that generates a compliant plan document and subtask tree. The skill automatically applies these constraints to the generated backlog items.

Can I generate a hierarchical subtask tree under an existing Backlog.md parent task?

Yes, you can generate a hierarchical subtask tree under an existing Backlog.md parent task by providing the parent task identifier. The system creates the subtree to reflect the plan tasks and progress structure.