skills.rest
Baronki
BaronkiCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

writing-plans

Generate implementation plans with file paths, tasks, tests, and commits.

1|Updated Mar 21, 2026
Search Tags:#planning#implementation#docs#tests#task-breakdown#git-commits
One-click install
npx skills add https://github.com/Baronki/KISWARM8.0 --skill writing-plans-baronki
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/Baronki/KISWARM8.0/tree/main/kiswarm7_remote/skills/writing-plans
Command: npx skills add https://github.com/Baronki/KISWARM8.0 --skill writing-plans-baronki

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps engineering teams create clear, executable implementation plans from vague specs, reducing guesswork and speeding delivery.

Core Features & Use Cases

  • Structured plan documents outlining required files, tests, docs, and commits.
  • Step-by-step task granularity aligned with DRY, YAGNI, and TDD principles.
  • Guidance for reproducible worktrees and actionable commit examples to track progress.

Quick Start

Provide a complete implementation plan for a feature, including task breakdown, required file changes, testing steps, and commit examples.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I turn a vague spec into an executable implementation plan?▼

Turning a vague spec into an executable implementation plan requires decomposing multi-step software tasks into granular tasks, exact file paths, testing steps, and explicit commands. This ensures structured task breakdown and reduces engineering guesswork.

What is the best way to break down software features into tasks for git commits?▼

Breaking down software features for git commits involves aligning step-by-step task granularity with TDD principles and providing actionable commit examples. This tracks progress through structured plan documents outlining required files and reproducible worktrees.

How do I generate a task breakdown that includes required file changes and testing steps?▼

Generating a task breakdown with required file changes and testing steps enforces a structured plan document format. It guides engineers through touched files, documentation updates, and explicit commands needed to reproduce results.

Can I use this implementation planning approach without existing code context?▼

Yes, this implementation planning approach is specifically applicable to situations with a written spec but limited code context. It guides engineers through task decomposition and version-control commits without requiring an established codebase.

Does structured implementation planning support TDD and DRY principles?▼

Structured implementation planning supports TDD, DRY, and YAGNI principles by enforcing step-by-step task granularity. This alignment ensures engineers generate focused testing steps and documentation within the comprehensive plan.

Related Skills

Explore More Software Engineering Skills→
Utchash007Utchash007

generate-tasks

Convert feature plan artifacts into TDD-ready task specifications embedded in PLAN-*.md files.

Community
Intermediate
JoaquinCampoJoaquinCampo
3

writing-plans

Generates executable software implementation plans from feature specs.

Community
Basic
MINT-IAMINT-IA

writing-plans

Converts a spec or requirements into a detailed implementation plan with tasks, files, tests, and commits.

Official
Intermediate
royhenengelroyhenengel

plan

Generate spec-driven implementation plans for software development tasks.

Community
Intermediate