skills.rest
Sjw2005
Sjw2005COMMUNITY
Explore all skills by this author →
GitHub

writing-plans

Convert vague project specifications into detailed implementation plans with tasks, milestones, and testing criteria.

Updated Aug 23, 2026
Search Tags:#planning#test-driven#software-engineering#task-decomposition#planning-docs#implementation-plans
One-click install
npx skills add https://github.com/Sjw2005/https---gitee.com-song-jiawei-2005-yolopro --skill writing-plans-sjw2005
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/Sjw2005/https---gitee.com-song-jiawei-2005-yolopro/tree/main/.agents/skills/writing-plans
Command: npx skills add https://github.com/Sjw2005/https---gitee.com-song-jiawei-2005-yolopro --skill writing-plans-sjw2005

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing clear, actionable implementation plans from vague specs is often manual, error-prone, and slows delivery.

Core Features & Use Cases

  • Structured task decomposition: breaks work into atomic tasks with clear interfaces.
  • Plan for code, tests, and docs: ensures coverage across engineering, QA, and docs.
  • Guided workstreams for iterative development and review checkpoints.

Quick Start

Provide a project spec or requirements and I will generate a complete, chunked implementation plan.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I convert vague project specifications into detailed implementation plans?▼

Implementation plans decompose multi-step software engineering work into atomic tasks with clear interfaces, testing criteria, and milestones, ensuring coverage across code, tests, and documentation for iterative development.

How do I create a task decomposition for a complex software refactoring project?▼

Task decomposition breaks complex refactoring or feature development into chunked, executable tasks with clear ownership, file-level responsibilities, and guided workstreams for iterative development and review.

Does generating implementation plans include test-driven development criteria?▼

Yes, generated implementation plans include test-driven development criteria by defining structured testing steps and QA coverage alongside code and documentation tasks within the plan document.

What is the best way to structure an implementation plan for multi-step feature development?▼

The best way to structure an implementation plan for feature development is using chunked task breakdowns that define clear ownership, milestones, version control commands, and review checkpoints for each workstream.

Can I use this approach for integration work and technical documentation updates?▼

Yes, this approach supports integration work and technical documentation updates by ensuring plan documents cover engineering, QA, and docs with structured task breakdowns and guided workstreams.

Related Skills

Explore More Software Engineering Skills→
dshearerdshearer
2

misatay-planning

Coordinate collaborative planning to decompose work into reviewable tasks with dependencies.

Community
Advanced
willdadywilldady
63

implement

Implement software features from ticket specifications with TDD and automated tests.

Community
Intermediate
Luney-IndustriesLuney-Industries
4

plan-task

Fetch Jira or Linear tickets and create implementation plans with security checks.

Official
Advanced
nahisahonahisaho
69

project-manager

Plan, schedule, and monitor software development projects with WBS and Gantt charts.

Community
Intermediate