writing-plans

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

2|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/FelixBitSoul/contentCrew-AI --skill writing-plans-felixbitsoul
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/FelixBitSoul/contentCrew-AI/tree/main/.trae/skills/writing-plans
Command: npx skills add https://github.com/FelixBitSoul/contentCrew-AI --skill writing-plans-felixbitsoul

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

当你有规格说明或需求用于多步骤任务时使用,在动手写代码之前确保计划清晰、可追溯。

Core Features & Use Cases

  • 将复杂特性拆解为具体任务、需要创建或修改的文件、测试和提交。
  • 生成专门的计划文档,指导开发与评审,节省时间并减少返工。
  • 适用于新功能开发、重构以及跨团队协同等场景。

Quick Start

描述一个特性或需求,并将其拆分为可执行的步骤,然后将计划保存到指定的文档位置。

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I break down complex software features into implementation plans?

Breaking down complex software features involves decomposing specifications into explicit tasks, file-level changes, tests, and commit guidance, saving the structured output to a dedicated plan document.

What is the best way to document task breakdown for multi-step software development?

Documenting task breakdown for multi-step software development means generating a structured plan document that organizes specific tasks, code changes, and tests to guide development and review.

How do I plan test-driven development steps before writing code?

Planning test-driven development steps before writing code means mapping deterministic multi-step tasks that include explicit file modifications and test requirements within a comprehensive implementation plan.

Does this planning approach work for cross-team software workflows?

This planning approach works for cross-team software workflows by generating comprehensive implementation plans that guide development and review, saving time and reducing rework across collaborating teams.

When do I need a dedicated plan document for software workflows?

You need a dedicated plan document for software workflows when handling complex specifications for multi-step tasks, ensuring your plan remains clear and traceable before starting to write code.