skills.rest
thesyntaxninja
thesyntaxninjaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

writing-plans

Generate structured multi-step plans with goals, context, and acceptance criteria.

2|Updated Mar 4, 2026
Search Tags:#workflow#planning#architecture#approval#project-management#task-decomposition#plan-writing
One-click install
npx skills add https://github.com/thesyntaxninja/syntaxninja-dojo --skill writing-plans-thesyntaxninja
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/thesyntaxninja/syntaxninja-dojo/tree/main/skills/writing-plans
Command: npx skills add https://github.com/thesyntaxninja/syntaxninja-dojo --skill writing-plans-thesyntaxninja

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning before implementation reduces ambiguity and rework by structuring tasks into concrete steps and context.

Core Features & Use Cases

  • Gather context and constraints before writing any implementation plan.
  • Produce a formal plan file detailing goals, steps, acceptance criteria, and review workflow.
  • Support plan-driven execution for architecture decisions and multi-file changes.

Quick Start

Draft a plan file at docs/plans/<date>-<slug>.md with goals, context, steps, and acceptance criteria, then present it for approval.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
What is the best way to plan complex software architecture changes before implementation?▼

Writing a plan for multi-file changes involves drafting a markdown file with goals, context, steps, and acceptance criteria. You then present this formal document for review and approval before proceeding with implementation.

How do I decompose complex project management tasks into actionable steps?▼

To decompose complex project management tasks, generate a formal plan document that breaks down work into structured, multi-step actions. This satisfies formal workflows by detailing goals, context, steps, and a review process.

How do I write a formal plan file for cross-team collaboration?▼

To write a formal plan file for cross-team collaboration, draft a markdown document detailing goals, context, steps, and acceptance criteria. Present this plan to clarify scope and secure formal approval from stakeholders.

When do I need a formal plan document for software engineering tasks?▼

A formal plan document is needed for software engineering tasks requiring architectural decisions, multi-file changes, or cross-team collaboration. It clarifies goals, scope, and acceptance criteria to reduce ambiguity and rework.

Can I use this planning workflow for tasks without architectural dependencies?▼

This planning workflow targets tasks requiring architectural decisions, multi-file changes, or cross-team collaboration. If your task lacks these complex dependencies, a formal multi-step plan may be unnecessary overhead.

Related Skills

Explore More Software Engineering Skills→
fredericpoitevinfredericpoitevin

clarify-before-research

Ask clarifying questions to define research goals and scope before starting.

Community
Basic
Hamad-CenterHamad-Center
3

drift-sync

Analyze code changes against Jira acceptance criteria and update CONTEXT.md.

Official
Advanced
EwallywEwallyw

team

Coordinate agent teams on shared task lists with staged pipeline execution.

Community
Advanced
bllshttngbllshttng
2

blueprint

Generate implementation blueprints with task lists and dependency checks from design documents.

Community
Advanced