sase_plan

Create and validate YAML implementation plans via the sase CLI.

5|Updated Dec 6, 2021

Search Tags:#workflow #planning #validation #implementation #agent #sase

Ready to run

npx skills add https://github.com/bbugyi200/dotfiles --skill sase-plan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sase_plan
Source: https://github.com/bbugyi200/dotfiles/tree/main/home/dot_codex/skills/sase_plan
Command: npx skills add https://github.com/bbugyi200/dotfiles --skill sase-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a rigorous framework for planning complex tasks, replacing native plan modes to ensure that implementation work is well-defined, validated, and phased before execution begins.

Core Features & Use Cases

Tiered Planning: Supports tale-level single-agent tasks and epic-level multi-phase projects with explicit dependencies.
Validation Workflow: Includes a mandatory validation step to ensure plan files meet schema requirements before proposal.
Use Case: Use this when you need to break down a large refactoring project into distinct, manageable phases that can be executed by different agents or in sequential steps.

Quick Start

Use the sase_plan skill to create a new plan file and validate it against the required schema before proposing it for execution.

Frequently Asked Questions about sase_plan

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

FAQPage Schema

How do I structure implementation plans for multi-agent software development tasks?▼

Structured implementation plans for software tasks use a tiered architecture, supporting single-agent tales and multi-phase epics with explicit dependency tracking to break down large refactoring projects before execution. This ensures work is well-defined and phased.

What is the best way to validate a development plan against a required schema before execution?▼

Validating a development plan requires running a mandatory validation step against a specific YAML schema before proposal. This ensures plan files meet schema requirements for lifecycle management via the command-line interface.

Can I use tiered planning for breaking down large refactoring projects into sequential phases?▼

Yes, tiered planning supports epic-level multi-phase projects with explicit dependencies. You can break down large refactoring projects into distinct, manageable phases executed by different agents or in sequential steps.

Do I need a specific command-line interface to manage the lifecycle of proposed implementation plans?▼

Yes, integration with the sase command-line interface is required for plan proposal and lifecycle management. It facilitates the creation and validation of structured implementation plans for software development tasks.

When should I replace my native plan mode with a structured validation workflow?▼

Replace native plan modes with a structured validation workflow when you need rigorous framework support for complex tasks, ensuring implementation work is well-defined, validated, and phased before execution begins.