mode-plan

Generate executable software-engineering plans without altering source code.

26|1|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/TeamSloppy/Sloppy --skill mode-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mode-plan
Source: https://github.com/TeamSloppy/Sloppy/tree/main/Sources/sloppy/Resources/Skills/mode-plan
Command: npx skills add https://github.com/TeamSloppy/Sloppy --skill mode-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan mode enables teams to generate concrete, executable plans for upcoming work without mutating the codebase, preserving safety and reproducibility.

Core Features & Use Cases

  • Structured, goal-driven planning prompts that produce step-by-step execution or investigation flows.
  • Documentation-first planning: capture context, risks, dependencies, acceptance criteria, and tests for handoff to Build-mode.
  • Use Case: a developer asks for a plan to investigate a bug or implement a feature, then exports a ready-to-run plan.

Quick Start

Provide a concrete, actionable plan for the requested task, detailing goals, steps, and validation without mutating any source files.

Frequently Asked Questions about mode-plan

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

FAQPage Schema
How do I create a software engineering plan without modifying source code?

A structured software engineering plan defines goals, context, scope, step-by-step flow, affected files, tests, risks, and acceptance criteria. It captures all necessary investigation details and project handoffs without mutating source files, ensuring reproducibility and safety.

How do I structure a bug investigation plan for a development team handoff?

To structure an investigation plan for handoff, document the goal, context, scope, step-by-step flow, affected modules, validation commands, risks, decisions, and open questions. This documentation-first approach provides a ready-to-run flow for the next developer.

What is the best way to document project scope and risks before implementation?

The best way to document project scope and risks before implementation is to generate a structured plan capturing context, dependencies, acceptance criteria, and tests. This documentation-first approach preserves safety by isolating planning from code mutations.

Can I generate step-by-step execution flows and validation commands for feature planning?

Yes, you can generate step-by-step execution flows and validation commands for feature planning. The plan details the entire execution flow and includes specific test and validation commands to verify acceptance criteria without touching source code.

Does Plan mode alter my repository files during the workflow planning phase?

Plan mode does not alter your repository files during the workflow planning phase. It strictly generates concrete, executable plans for software-engineering tasks, preserving codebase safety and reproducibility until you transition to Build mode.