skills.rest
tusosos
tusososCOMMUNITY
Explore all skills by this author →
GitHub

writing-plans

Convert written specifications into detailed software development plans with file mappings.

Updated Apr 3, 2026
Search Tags:#planning#documentation#spec-to-plan#task-decomposition#planning-skills#software-planning
One-click install
npx skills add https://github.com/tusosos/manus-knowledge-base --skill writing-plans-tusosos
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/tusosos/manus-knowledge-base/tree/main/skills/writing-plans
Command: npx skills add https://github.com/tusosos/manus-knowledge-base --skill writing-plans-tusosos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams translate a written spec or requirements into a comprehensive, executable plan before any code is written, reducing ambiguity and rework.

Core Features & Use Cases

  • Generates a detailed, task-by-task plan that covers scope, file structure, tests, docs, and validation steps.
  • Maps required changes to exact files and artifacts, ensuring traceability from planning to delivery.
  • Supports multi-subsystem projects and complex features by decomposing work into manageable tasks with clear milestones.

Quick Start

Provide a feature spec and I will generate a complete, ready-to-execute 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 turn a software specification into an actionable implementation plan?▼

To turn a software specification into an implementation plan, provide the spec to generate a detailed, task-by-task document covering scope, file mappings, tests, and validation steps for execution.

What is the best way to decompose complex features into manageable development tasks?▼

Decomposing complex features involves mapping required changes to exact files and artifacts, breaking work into clear milestones for multi-subsystem projects to ensure traceability from planning to delivery.

Can I generate file structure and test plans directly from a written feature spec?▼

Yes, generating file structure and test plans from a written feature spec produces a comprehensive document that maps exact file changes, required tests, and documentation to reduce ambiguity before coding.

Does this planning approach work for multi-subsystem software projects?▼

This planning approach works for multi-subsystem software projects by decomposing complex features into manageable tasks with clear milestones and mapping them to exact files across different subsystems.

Why do I need to map file changes and tests before writing any code?▼

Mapping file changes and tests before writing code reduces ambiguity and rework by ensuring traceability from planning to delivery, providing clear validation steps and commit guidance for development.

Related Skills

Explore More Software Engineering Skills→
shichengwuyushichengwuyu
4

writing-plans

Generate implementation-ready plans from written specifications for multi-file software tasks.

Community
Advanced
underPressueunderPressue

writing-plans

Converts a project specification into a step-by-step implementation plan with tasks, files, tests, and milestones.

Community
Intermediate
vincent-ngvincent-ng

writing-plans

Translate vague specifications into concrete, testable implementation plans.

Community
Intermediate
mazicimertmazicimert

press-media

Guide press-kit preparation, journalist outreach, and embargo planning for indie developers.

Community
Intermediate