workflows-plan

Transform feature descriptions into structured project plans with acceptance criteria.

Updated Mar 3, 2026
One-click install
npx skills add https://github.com/The-Rabak/naysmith --skill workflows-plan-the-rabak
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workflows-plan
Source: https://github.com/The-Rabak/naysmith/tree/main/.github/skills/workflows-plan
Command: npx skills add https://github.com/The-Rabak/naysmith --skill workflows-plan-the-rabak

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams convert feature descriptions, bugs, or improvement ideas into structured, plan-first documents that follow established conventions, reducing planning time and increasing consistency across initiatives.

Core Features & Use Cases

  • Plan generation: Converts narrative inputs into issue-ready planning documents with defined scope, milestones, and acceptance criteria.
  • Template-driven: Applies standard planning templates to maintain consistency across plans.
  • Versatile inputs: Accepts feature descriptions, bug reports, or improvements and outputs execution-ready plans that integrate with issue trackers and workflows.

Quick Start

Provide a feature description and let workflows-plan generate a complete planning document that follows the team's established conventions.

Frequently Asked Questions about workflows-plan

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

FAQPage Schema
How do I turn feature descriptions into structured project plans?

Turn feature descriptions into structured project plans by applying standard planning templates to narrative inputs, generating issue-ready documents with defined scope, milestones, and acceptance criteria.

Can I generate issue-ready plans from bug reports?

Generate issue-ready plans from bug reports by processing improvement ideas and bug narratives into execution-ready tasks complete with dependency maps and acceptance criteria.

How to map dependencies for execution-ready tasks?

Map dependencies for execution-ready tasks by transforming feature descriptions into structured plans that output dependency maps suitable for downstream workflows and issue trackers.

Does this planning approach work for both feature requests and improvement ideas?

This planning approach works for feature requests, bug reports, and improvement ideas, converting versatile narrative inputs into execution-ready plans that integrate with issue trackers.

How do I generate acceptance criteria for project management templates?

Generate acceptance criteria for project management templates by converting narrative feature descriptions into structured planning documents with defined scope and execution-ready tasks.