plan-writing

Name: plan-writing
Availability: InStock
Author: BeastAyyG

Break complex work into actionable tasks with dependencies and verification criteria.

1|Updated Feb 14, 2026

Search Tags:#requirements #dependencies #verification #project-management #task-planning #plan-writing

Ready to run

npx skills add https://github.com/BeastAyyG/Campus-Cupids --skill plan-writing-beastayyg

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plan-writing
Source: https://github.com/BeastAyyG/Campus-Cupids/tree/main/.agent_backup/skills/plan-writing
Command: npx skills add https://github.com/BeastAyyG/Campus-Cupids --skill plan-writing-beastayyg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Structured task planning with clear breakdowns, dependencies, and verification criteria. Use when implementing features, refactoring, or any multi-step work.

Core Features & Use Cases

Small, focused tasks with independent verification
Dependency-aware sequencing and phase-less planning
Dynamic naming of plan files saved at the project root

Quick Start

Create a concise, verifiable task plan for the feature and save it as a {task-slug}.md file in the project root.

Frequently Asked Questions about plan-writing

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

FAQPage Schema

How do I break down multi-step project work into verifiable tasks?▼

Breaking down multi-step project work involves splitting features or refactoring into small, focused tasks with independent verification criteria. This approach ensures every step is actionable and validated before moving forward.

What is dependency-aware sequencing in task planning?▼

Dependency-aware sequencing in task planning is organizing tasks based on their explicit relationships rather than rigid phases. It maps dependencies to ensure prerequisite work is completed before dependent tasks begin, producing a runnable plan.

How do I create a runnable plan for feature development?▼

You create a runnable plan for feature development by defining project-specific task granularity and mapping explicit dependencies. The plan is then saved as a dynamically named `{task-slug}.md` file in your project root.

Can I use this approach for both refactoring and new feature implementation?▼

Yes, you can use this task planning approach for both refactoring and new feature implementation. It is designed for any multi-step project that requires breaking down complex work into actionable, verifiable components.

What's the best way to name and store plan files for a project?▼

The best way to store plan files is to save them directly at the project root using a simple naming convention. Files are dynamically named as `{task-slug}.md` to maintain organization and accessibility.