skills.rest
mopeyjellyfish
mopeyjellyfishCOMMUNITY
Explore all skills by this author →
GitHub

plan

Convert unstructured requirements into structured execution-ready plans with dependencies and testing strategies.

1|Updated Apr 18, 2026
Search Tags:#workflow#planning#testing#architecture#documentation#requirements#implementation-units
One-click install
npx skills add https://github.com/mopeyjellyfish/flywheel --skill plan-mopeyjellyfish
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/mopeyjellyfish/flywheel/tree/main/skills/plan
Command: npx skills add https://github.com/mopeyjellyfish/flywheel --skill plan-mopeyjellyfish

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Transform ambiguous requirements, brainstorms, or feature ideas into durable, execution-ready plans that guide implementation and enable confident handoffs.

Core Features & Use Cases

  • Generate a structured plan from a requirements doc, bug report, or idea.
  • Define concrete implementation units, dependencies, testing strategy, and risk notes.
  • Provide a repeatable workflow that separates planning from execution and supports reviews.

Quick Start

Plan from a requirements doc or idea by invoking the plan workflow to generate a structured plan for execution.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I turn unstructured requirements into an execution-ready plan?▼

To turn unstructured requirements into an execution-ready plan, provide your requirements doc, bug report, or feature idea. The workflow defines implementation units, dependencies, testing strategies, and risk assessments to guide software execution.

What is the best way to document software architecture decisions for handoff?▼

Documenting software architecture decisions for handoff involves recording decisions, rationale, and acceptance criteria in a structured plan. This separates planning from execution and enables confident reviews and repeatable implementation workflows.

Can I generate a testing strategy from a feature idea before implementation?▼

Yes, you can generate a testing strategy from a feature idea before implementation. The workflow processes your feature idea to detail concrete testing strategies, risk notes, and acceptance criteria alongside implementation units.

Does the planning workflow support bug reports as input?▼

Yes, the planning workflow supports bug reports as input alongside requirements docs and ideas. It transforms these ambiguous inputs into structured plans detailing implementation units, dependencies, and risk assessments for execution.

How do I separate planning from execution in a software workflow?▼

To separate planning from execution in a software workflow, generate a structured plan artifact that records decisions and implementation units. This provides a repeatable workflow that supports reviews before any execution begins.

When do I need to define implementation units and dependencies for a software task?▼

You need to define implementation units and dependencies for a software task when transitioning from ambiguous requirements to execution-ready plans. This structured approach ensures confident handoffs and repeatable execution workflows.

Related Skills

Explore More Software Engineering Skills→
The-RabakThe-Rabak

workflows-plan

Transform feature descriptions into structured project plans with acceptance criteria.

Community
Advanced
centminmodcentminmod
30

ai-cross-verifier

Cross-verify Claude-generated plans and code with Codex and Gemini.

Community
Intermediate
dthuy62dthuy62

ck:plan

Create detailed technical implementation plans with phases and dependency tracking.

Community
Advanced
robzilla1738robzilla1738
660

supergoal

Automate planning, execution, and verification of complex software tasks with Python.

Community
Advanced