af-plan

Generate a critiqued software plan using the GODS framework with a whiteboard.md output.

3|Updated Oct 5, 2025
One-click install
npx skills add https://github.com/korchasa/ide-rules --skill af-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: af-plan
Source: https://github.com/korchasa/ide-rules/tree/main/catalog/skills/af-plan
Command: npx skills add https://github.com/korchasa/ide-rules --skill af-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables autonomous, critique-driven planning for software tasks, capturing a robust plan in a single whiteboard document.

Core Features & Use Cases

  • Pure Planning: Creates a critique-based plan without implementing code.
  • Plan Management: Uses a task management tool to track steps.
  • Proactive Uncertainty Resolution: Identifies gaps and resolves uncertainties during planning.
  • Documentation Output: Writes results to ./documents/whiteboard.md.
  • Use Case: Planning a complex feature with risk assessment prior to coding.

Quick Start

Create a critiqued plan in ./documents/whiteboard.md using the GODS framework.

Frequently Asked Questions about af-plan

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

FAQPage Schema
How do I create a critiqued project plan for a complex software feature?

To create a critiqued project plan, you can use the GODS framework to generate a structured plan in a whiteboard document. It proactively identifies gaps and resolves uncertainties during planning without writing code.

What is the GODS framework for software task planning?

The GODS framework is a planning methodology that generates structured, critique-driven plans for software tasks. It produces a formal Definition of Done and outputs results directly to a whiteboard document.

Does this planning approach write any implementation code?

No, this approach provides pure planning only and does not write implementation code. It focuses entirely on architecture decisions, task breakdowns, and explicit verification steps before development begins.

How do I manage task breakdowns and track project steps before coding?

You can manage task breakdowns by generating a structured plan that uses a task management tool to track steps. The plan captures all steps and a formal Definition of Done in a whiteboard document.

Where does the generated project plan documentation get saved?

The generated project plan documentation is saved as a whiteboard document at ./documents/whiteboard.md. This file captures the complete critique-based plan and formal Definition of Done.

When should I use a critique-driven planning approach for development projects?

Use critique-driven planning when you need proactive uncertainty resolution for complex features and architecture decisions. It is ideal for risk assessment and task breakdowns prior to coding.