skills.rest
ferundatattoo
ferundatattooCOMMUNITY
Explore all skills by this author →
GitHub

deep-plan

Orchestrate a multi-phase planning workflow for complex software features.

Updated Aug 27, 2026
Search Tags:#planning#tdd#architecture#documentation#feature#risk-management#stakeholder-interview
One-click install
npx skills add https://github.com/ferundatattoo/ethereal --skill deep-plan-ferundatattoo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: deep-plan
Source: https://github.com/ferundatattoo/ethereal/tree/main/.claude/skills/deep-plan
Command: npx skills add https://github.com/ferundatattoo/ethereal --skill deep-plan-ferundatattoo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning complex software features requires coordinating research, stakeholder interviews, external reviews, and a formal implementation plan to reduce risk and align teams.

Core Features & Use Cases

  • Multi-phase workflow: Research → Interview → External Review → TDD Plan → Sections.
  • Generates structured planning artifacts saved under docs/planning/{feature}/...
  • Supports architecture decisions, risk assessments, dependency sequencing, and gate criteria.

Quick Start

Describe a feature with 5+ files and run the planning workflow to produce a phased plan.

Frequently Asked Questions about deep-plan

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

FAQPage Schema
How do I plan a complex software feature across multiple components?▼

To plan a complex software feature across multiple components, use a structured multi-phase workflow that coordinates research, stakeholder interviews, external reviews, and TDD planning to produce formal implementation plans.

What is the best way to document architecture decisions and risk assessments for feature planning?▼

The best way to document architecture decisions and risk assessments is to generate structured planning artifacts under docs/planning paths, ensuring dependency ordering and gate criteria are formally captured.

How do I structure a TDD plan for a feature touching multiple files?▼

To structure a TDD plan for a feature touching multiple files, run a phased planning workflow that progresses through research, interviews, external reviews, and finally sections dedicated to test-driven development planning.

When do I need formal stakeholder interviews for feature planning?▼

You need formal stakeholder interviews for feature planning when dealing with complex features that require external reviews, risk management, and alignment across teams before creating a formal implementation plan.

Can I use this planning workflow for features with less than five files?▼

This planning workflow is designed for complex features touching multiple components and requiring formal research, so features with fewer than five files likely do not need this level of multi-phase planning.

Does feature planning include dependency ordering and gate criteria?▼

Feature planning includes dependency ordering and gate criteria by satisfying requirements for architecture decisions and risk assessment, exporting structured documents to docs/planning paths to align teams.

Related Skills

Explore More Product & Management Skills→
alex-voloshin-devalex-voloshin-dev
2

product

Transform raw feature inputs into structured product requirements and feature briefs.

Community
Advanced
cbgbtcbgbt
5

implement-commit

Execute commits from TOML implementation plans via a deterministic TDD pipeline.

Community
Advanced
foolpoet44foolpoet44
1

userstory-documentation

Translate PRDs into epics, user stories, and acceptance criteria.

Community
Advanced
doolindoolin

self-host-development-light

Create Markdown project management templates under a .development directory.

Community
Basic