writing-plans

Generate structured implementation plans with tasks, files, tests, docs, and commit steps.

Updated Feb 5, 2026
One-click install
npx skills add https://github.com/tyk-lab/my-ai-skill --skill writing-plans-tyk-lab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/tyk-lab/my-ai-skill/tree/main/skills/writing-plans
Command: npx skills add https://github.com/tyk-lab/my-ai-skill --skill writing-plans-tyk-lab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps engineers map out step-by-step implementation plans before coding, bridging context gaps and ensuring alignment across tasks, files, tests, and docs.

Core Features & Use Cases

  • Create comprehensive, task-level implementation plans from a given feature or requirement.
  • Define required files, tests, docs, and commit steps to guide engineering work.
  • Ideal for starting new software features or big refactors where detailed planning reduces rework and ambiguity.

Quick Start

Use the writing-plans skill to craft a complete implementation plan from a given feature name and requirements.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I create an implementation plan from a feature specification?▼

Breaking down feature requirements into an implementation plan involves mapping task steps, required files, tests, and documentation into a structured template. This defines step-by-step commit guidance to align engineering work and reduce rework before coding begins.

What is task breakdown in software engineering planning?▼

Task breakdown in software engineering planning is mapping a feature into step-by-step tasks, required files, tests, and documentation. It bridges context gaps across teams by defining a structured plan template with specific commit guidance for each engineering step.

How do I map out tasks, files, and tests before starting a new software feature?▼

Mapping out tasks, files, and tests requires generating a detailed implementation plan from the feature requirements. This defines a structured template with header sections, task steps, file references, and step-by-step commit guidance to direct the engineering work.

Does detailed implementation planning help with big software refactors?▼

Detailed implementation planning helps with big software refactors by mapping task steps, files, tests, and documentation before coding. This reduces rework and ambiguity by ensuring alignment across teams through a structured plan template with step-by-step commit guidance.

What's the best way to structure step-by-step commit guidance for a new feature?▼

Structuring step-by-step commit guidance is best done by generating a detailed implementation plan that defines required files, tests, docs, and task steps. This approach provides a structured template bridging context gaps and ensuring alignment across engineering work.