skills.rest
simon-downes
simon-downesCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

workflow-plan

Plan complex projects into executable artifacts with four-phase workflows.

1|Updated Oct 5, 2025
Search Tags:#design#planning#requirements#execution#milestones#phases#rfc2119
One-click install
npx skills add https://github.com/simon-downes/agent-workspace --skill workflow-plan-simon-downes
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: workflow-plan
Source: https://github.com/simon-downes/agent-workspace/tree/main/skills/workflow-plan
Command: npx skills add https://github.com/simon-downes/agent-workspace --skill workflow-plan-simon-downes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning a new project or feature often starts as vague intent. This skill guides you through a structured, four-phase process that converts ambiguity into a concrete, executable plan artifact you can reference in future sessions.

Core Features & Use Cases

  • Four-phase planning workflow: Objective & Requirements, Technical Design, Milestones, and Review, all captured as a cohesive plan.
  • RFC 2119-compliant requirements drafting: Ensures testable, observable criteria are defined early to guide implementation.
  • Plan artifact delivery: Produces a self-contained plan document that can be handed to a new team or session to execute without remaining questions.
  • Use Case: When starting a new feature, rewrite vague goals into explicit objectives, design decisions, milestones, and acceptance criteria before coding begins.

Quick Start

Begin by writing a clear Objective for your project in Phase 1 and draft testable requirements using RFC 2119 language.

Frequently Asked Questions about workflow-plan

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

FAQPage Schema
How do I turn vague project intent into an executable plan?▼

Drafting project requirements requires defining testable, observable criteria early. Using RFC 2119 language ensures your requirements are explicit and structured, guiding implementation and minimizing ambiguity before coding begins.

What is the best way to structure milestones for a new software feature?▼

Structuring milestones for a new software feature involves defining explicit phases within your plan artifact. This approach captures design decisions and acceptance criteria, ensuring the resulting milestones are complete and executable by a new team.

Can I use this planning workflow for startup initiatives and research tasks?▼

Yes, you can use this planning workflow for startup initiatives and research tasks. The structured requirements and design decision phases apply to any complex project requiring peer review and clear objectives before implementation begins.

Does the generated plan artifact remain usable in future sessions?▼

Yes, the generated plan artifact remains usable in future sessions. It is self-contained, capturing all requirements, design decisions, and milestones so a new team or session can execute the plan without remaining questions.

When should I not use a structured project planning workflow?▼

You should not use a structured project planning workflow for simple tasks lacking ambiguity. This process is designed for complex projects requiring detailed requirements drafting, technical design decisions, and milestone definition before implementation.

Related Skills

Explore More Software Engineering Skills→
WILLOSCARWILLOSCAR
497

tutorial-spec

Generate a TUTORIAL_SPEC.md from STATUS.md, GOAL.md, and DECISIONS.md.

Community
Intermediate
mezivillagermezivillager
1

planning

Generate bite-sized implementation task plans from approved designs.

Community
Intermediate
HeldinhowHeldinhow
4

cicd-github-actions

Generate GitHub Actions CI/CD pipelines for automated builds, tests, and deployments.

Community
Intermediate
awood45awood45
11

requirements-doc

Transform unstructured product ideas into formal requirements documents with RFC 2119 requirements.

Community
Advanced