writing-plans

Decompose large coding tasks into plans with goals, scope, and acceptance gates.

11|3|Updated Feb 24, 2026
One-click install
npx skills add https://github.com/Threat-Vector-Security/guardian-agent --skill writing-plans-threat-vector-security
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/Threat-Vector-Security/guardian-agent/tree/main/skills/writing-plans
Command: npx skills add https://github.com/Threat-Vector-Security/guardian-agent --skill writing-plans-threat-vector-security

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams and individuals craft comprehensive implementation plans for large coding tasks, enabling structured decomposition before editing.

Core Features & Use Cases

  • Planning framework: explicitly defines goals, scope, acceptance criteria, and checks to reuse.
  • Task decomposition: breaks work into manageable tasks with gates, verifications, and rollout hints.
  • Use cases: ideal for multi-file projects, architecture changes, and complex refactors where upfront planning reduces risk.

Quick Start

Ask me to generate a detailed implementation plan for your project, including goals, scope, tasks, and acceptance gates.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I break down a large coding task into manageable steps?

Task decomposition for architecture changes breaks work into manageable sub-tasks with explicit gates, verifications, and rollout hints. This planning approach reduces risk by defining goals, scope, and acceptance criteria before editing complex refactors.

What is the best way to plan a multi-file project refactor before coding?

The best way to plan a multi-file project refactor is to generate a comprehensive implementation plan outlining goals, scope, tasks, and acceptance gates. Upfront planning structures the architecture changes and reduces execution risk.

When do I need a planning framework for software engineering tasks?

You need a planning framework for software engineering tasks involving complex refactors, architecture changes, or multi-file projects. These substantial tasks benefit from upfront decomposition to establish clear scope and acceptance gates before editing.

How do I define acceptance gates for a coding task decomposition?

You define acceptance gates for coding task decomposition by establishing explicit verifications and reusable checks within the implementation plan. This ensures each manageable task meets the defined scope and goals before rollout.

Can I use this planning framework for single-file code updates?

This planning framework is designed for substantial tasks like multi-file projects, architecture changes, and complex refactors. Single-file code updates do not typically require the upfront task decomposition and acceptance gates this approach provides.