skills.rest
Shade666
Shade666COMMUNITY
Explore all skills by this author →
GitHub

Radberi-PlanWrite

Convert user requirements into structured task-level plans with acceptance criteria.

1|Updated Mar 20, 2026
Search Tags:#planning#requirements#backlog#project-management#acceptance-criteria#task-breakdown
One-click install
npx skills add https://github.com/Shade666/huml-dotnet --skill radberi-planwrite
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Radberi-PlanWrite
Source: https://github.com/Shade666/huml-dotnet/tree/main/.claude/skills/Radberi-PlanWrite
Command: npx skills add https://github.com/Shade666/huml-dotnet --skill radberi-planwrite

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Planning complex software work by turning requirements, specs, backlog items, or feature requests into a structured, executable plan before coding.

Core Features & Use Cases

  • Converts requirements into task-level plans with clear scope and milestones
  • Supports traceability across backlog items, issues, and conversations
  • Produces a reusable plan structure that includes tasks, dependencies, acceptance criteria, and references for quick handoff

Quick Start

Provide a feature description and any constraints, and Radberi-PlanWrite will generate an approval-ready plan with tasks, dependencies, and acceptance criteria.

Frequently Asked Questions about Radberi-PlanWrite

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

FAQPage Schema
How do I break down software requirements into structured task plans?▼

Breaking down software requirements into structured task plans involves transforming feature descriptions and constraints into actionable items with clear scope, milestones, dependencies, and acceptance criteria for traceability.

What is the best way to generate acceptance criteria for a backlog grooming session?▼

Generating acceptance criteria for backlog grooming is achieved by automating the transformation of user requirements into approval-ready plans. This process ensures each task includes defined acceptance criteria and traceability to source issues or conversations.

Can I use automated task breakdown for complex multi-file refactoring?▼

Automated task breakdown supports complex multi-file refactoring by applying structured planning artifacts. It converts refactor requirements into executable plans with task dependencies, milestones, and references for quick development handoff.

Do I need specific project management tools to trace backlog items and dependencies?▼

Specific external project management tools are not required to trace backlog items and dependencies. The planning process natively supports traceability across backlog items and conversations by producing a reusable plan structure with embedded references.

How to plan multi-step software work before coding begins?▼

Planning multi-step software work before coding requires converting specs or feature requests into an approval-ready plan. This defines the exact tasks, scope, and milestones needed to execute the work with confidence.

Related Skills

Explore More Product & Management Skills→
amingclawdevamingclawdev
26

aming-claw-project-inbox

Capture raw user requirements and coordinate Capture and Confirmation modes for backlog promotion via governance endpoints.

Community
Intermediate
AnastasiyaWAnastasiyaW
140

plan-to-tickets

Decompose project plans into Markdown tickets with acceptance criteria.

Community
Intermediate
sumpalabssumpalabs
10

to-prd

Synthesize project conversations and codebase context into structured PRDs.

Official
Intermediate
ajstack22ajstack22

atlas-agent-product-manager

Automates backlog grooming and user-story creation across Atlas workflows with acceptance-criteria validation.

Community
Advanced