skills.rest
tctinh
tctinhCOMMUNITY
Explore all skills by this author →
GitHub

writing-plans

Generate bite-sized implementation plans with file modifications, testing steps, and commit strategies.

160|20|Updated Jan 4, 2026
Search Tags:#planning#developer workflow#code generation#task breakdown#test-driven development#implementation plan
One-click install
npx skills add https://github.com/tctinh/agent-hive --skill writing-plans-tctinh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/tctinh/agent-hive/tree/main/packages/opencode-hive/skills/writing-plans
Command: npx skills add https://github.com/tctinh/agent-hive --skill writing-plans-tctinh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of detailed, step-by-step implementation plans for software development tasks, ensuring clarity and reducing ambiguity for engineers.

Core Features & Use Cases

  • Comprehensive Planning: Generates plans that assume zero prior context, detailing file modifications, code snippets, testing procedures, and commit strategies.
  • Bite-Sized Tasks: Breaks down complex features into small, manageable actions (2-5 minutes each).
  • Use Case: When starting a new feature, use this Skill to generate a complete plan, including failing tests, minimal implementations, and commit messages, ensuring a structured and test-driven development process.

Quick Start

Use the writing-plans skill to create an implementation plan for adding a new user authentication module.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I generate an implementation plan for a new software feature?▼

An implementation plan for a new feature is generated by breaking down the task into bite-sized actions, detailing specific file modifications, code snippets, testing procedures, and commit strategies.

What is the best way to break down complex development tasks into manageable steps?▼

The best way to break down complex tasks is generating a structured plan with small 2-5 minute actions, assuming zero prior codebase context, ensuring clarity and reducing ambiguity for engineers.

Can I create a test-driven development plan that includes commit strategies?▼

Yes, you can create a test-driven development plan that includes failing tests, minimal implementations, and commit messages, adhering to TDD and DRY principles throughout the workflow.

Does this planning approach require prior codebase context to outline file modifications?▼

No prior codebase context is required; the planning process assumes zero existing context and explicitly outlines specific file modifications and code implementations needed for the feature.

How do implementation plans handle task dependencies and verification criteria?▼

Implementation plans handle task dependencies and verification criteria by structuring the workflow with clear task sequences, ensuring each bite-sized step is verified before moving forward.

Why should I use an automated task breakdown for software development?▼

An automated task breakdown should be used to ensure structured, test-driven development, reducing ambiguity by detailing exact code implementations, testing steps, and commit strategies.

Related Skills

Explore More Software Engineering Skills→
fsollafsolla

spec-driven-development

Enforce a mandatory specification phase before code implementation.

Community
Advanced
starwardsstarwards
42

writing-plans

Draft detailed implementation plans with file paths, code snippets, and verification steps.

Official
Basic
helmordevhelmordev

executing-plans

Execute implementation plans in verified task batches with periodic review.

Community
Intermediate
royhenengelroyhenengel

plan

Generate spec-driven implementation plans for software development tasks.

Community
Intermediate