skills.rest
arthur-debert
arthur-debertCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

planning

Plan a feature from loose ideas into a structured delivery workflow.

Updated Apr 14, 2026
Search Tags:#planning#adr#decomposition#spec#feature#tickets#epic
One-click install
npx skills add https://github.com/arthur-debert/dodot --skill planning-arthur-debert
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: planning
Source: https://github.com/arthur-debert/dodot/tree/main/.agents/skills/planning
Command: npx skills add https://github.com/arthur-debert/dodot --skill planning-arthur-debert

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you turn a loose feature or epic idea into a structured planning flow, so you can move from brainstorming to a locked spec, architecture decisions, and execution tickets without skipping critical checkpoints.

Core Features & Use Cases

  • Feature ideation and naming: Shapes an initial concept into a clear, shared feature name and direction.
  • Spec and ADR sequencing: Produces the authoritative spec first, then the architectural decisions that depend on it.
  • Epic and ticket decomposition: Breaks a larger initiative into an execution-ready epic and work-stream issues after the spec is approved.
  • Human checkpoints: Pauses at the right moments for approval before moving to the next phase.
  • Use case: A product team wants to launch a new platform capability and needs help organizing the idea, writing the spec, documenting decisions, and splitting the work into issues.

Quick Start

Ask the planning skill to help you turn a new feature idea into an overview and spec-ready plan.

Frequently Asked Questions about planning

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

FAQPage Schema
How do I turn a loose feature idea into a structured spec and execution tickets?▼

Feature planning requires staged checkpointing to shape concepts into a locked spec, capture architectural decisions, and decompose the epic into execution-ready tickets before implementation.

What is the best way to sequence specs and architectural decision records for a new epic?▼

Sequencing specs and ADRs requires producing the authoritative specification first, then documenting the architectural decisions that depend on that approved spec before breaking down the work.

How do I decompose a complex product epic into work-stream tickets?▼

Epic decomposition happens after spec approval, breaking a larger initiative into an execution-ready epic and granular work-stream issues to ensure structured delivery without skipping checkpoints.

When do I need human checkpoints in the feature planning workflow?▼

Human checkpoints are needed during feature planning to pause for approval at critical moments, ensuring the spec is locked and architecture decisions are reviewed before moving to ticket decomposition.

Can I use this planning flow for early-stage product ideation and naming?▼

Yes, early-stage product ideation and naming is supported, shaping an initial loose concept into a clear, shared feature name and direction before moving into specification and architectural sequencing.

Does epic-to-ticket breakdown work without a fully approved specification?▼

No, epic and ticket decomposition requires a locked specification first. The planning workflow enforces spec-first sequencing to ensure execution tickets are generated only after the spec is approved.

Related Skills

Explore More Product & Management Skills→
dikinidikini

bk-explore

Guide conversational exploration of feature ideas through targeted questions.

Community
Intermediate
Khamel83Khamel83

implement-plan

Execute approved implementation plans with persistent beads-backed task tracking.

Community
Advanced
timothyshentimothyshen

spec-master

Organize specifications, plans, tasks, issues, ADRs, and change logs in a structured directory.

Community
Advanced
clearsmogclearsmog
2

mindmap

Generate PNG or SVG mind map images from mind-elixir plaintext content.

Community
Intermediate