gf-plan

Research context and generate a grounded plan with a test checklist.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/ricky-yosh/agent-workflows --skill gf-plan-ricky-yosh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gf-plan
Source: https://github.com/ricky-yosh/agent-workflows/tree/main/skills/greenfield/gf-plan
Command: npx skills add https://github.com/ricky-yosh/agent-workflows --skill gf-plan-ricky-yosh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Greenfield planning often lacks a structured, end-to-end approach. gf-plan helps teams research context, identify scope, and generate a grounded plan that can be reviewed and approved before implementation.

Core Features & Use Cases

  • Research the task context (progress files, specs) to inform planning decisions.
  • Identify the task scope and constrain planning to the identified task(s) only.
  • Produce a complete plan that references existing code patterns and ends with a testable How to test checklist.

Quick Start

Describe the next greenfield task and let gf-plan generate a recommended plan for user confirmation.

Frequently Asked Questions about gf-plan

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

FAQPage Schema
How do I plan a greenfield coding task from scratch?

Planning a greenfield task involves researching context, identifying scope, and generating an actionable plan. This approach constrains planning to the specific task and references existing codebase patterns before implementation begins.

What is a greenfield plan-mode workflow in software engineering?

A greenfield plan-mode workflow is a structured planning process for new initiatives. It researches task context, justifies recommendations, and requires user confirmation before delivering a grounded plan with a testable checklist.

How do you scope a greenfield feature to avoid overplanning?

Scoping a greenfield feature requires identifying the specific task boundaries first. You then constrain all planning decisions to that identified scope only, ensuring the generated plan stays focused and actionable for the user.

Do I need existing code patterns to plan a greenfield project?

Existing code patterns are not strictly required but are highly recommended for greenfield planning. Referencing established codebase familiarity helps justify recommendations and ensures the new plan aligns with current architecture.

What's the best way to validate a greenfield implementation plan?

The best way to validate a greenfield plan is through a concrete "How to test" checklist. This checklist provides incremental task validation steps, ensuring the plan is testable and grounded before any code is written.

Can I use structured planning for single-task greenfield initiatives?

Structured planning applies directly to single-task greenfield initiatives. It handles scope identification, codebase research, and delivers a complete plan with user confirmation, ensuring the single task is fully scoped before implementation.