plan

Create a detailed plan for your software project before writing any code.

1|Updated May 16, 2026
One-click install
npx skills add https://github.com/devMoez/titan --skill plan-devmoez
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/devMoez/titan/tree/main/skills/software-development/plan
Command: npx skills add https://github.com/devMoez/titan --skill plan-devmoez

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

It helps you move from an ambiguous request to a concrete, actionable plan without making any code changes or running commands.

Core Features & Use Cases

  • Plan-only workflow: Produces a markdown plan for the current task instead of implementing or executing it.
  • Workspace-safe behavior: Writes only the plan file into .Titan/plans/ and avoids mutating commands, commits, pushes, or external actions.
  • Actionable structure: Generates goal, assumptions, approach, step-by-step plan, likely files, validation steps, and risks/tradeoffs when relevant.
  • Use Case: When you want to implement a feature but need clarity first (e.g., “Add a new API endpoint and update the UI”), use this skill to outline exactly what will change and how it will be verified.

Quick Start

Ask the agent to plan the implementation for your request and save the resulting markdown plan under .Titan/plans/.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I create an implementation plan for a software task without modifying the codebase?

You can generate a concrete implementation plan without modifying code by outlining the goal, approach, step-by-step instructions, likely file modifications, and validation steps into a markdown file saved under `.Titan/plans/`.

What is the best way to structure a workflow plan before making repo changes?

A structured workflow plan should include the goal, assumptions, approach, step-by-step actions, likely files to modify, validation steps, and potential risks or tradeoffs to ensure clarity before executing repo changes.

How do I outline likely file modifications and validation steps for a new feature?

To outline file modifications and validation steps, you generate a markdown plan that identifies the target files, details the ordered approach for changes, and specifies the exact validation steps required to verify the implementation.

Does the planning workflow execute commands or push commits to the repository?

No, the planning workflow follows strict safety constraints that avoid executing mutating commands, pushing commits, or taking external actions, ensuring the repository remains entirely unchanged.

Can I use markdown planning to clarify ambiguous software requests before implementation?

Yes, markdown planning transforms ambiguous software requests into actionable plans by defining assumptions, identifying likely files, and detailing a step-by-step approach to clarify the implementation path before any coding begins.

When should I not use a plan-only workflow for my coding task?

You should avoid a plan-only workflow when your task requires immediate code execution, direct file modifications, or running commands, because this approach strictly generates a markdown plan without implementing the requested changes.