Outline goals, architecture, and tasks in a structured plan file.
npx skills add https://github.com/Jamie-Cui/magent --skill writing-plans-jamie-cui
Please help me install this Agent Skill. Skill: writing-plans Source: https://github.com/Jamie-Cui/magent/tree/main/skills/writing-plans Command: npx skills add https://github.com/Jamie-Cui/magent --skill writing-plans-jamie-cui
This Skill helps teams outline multi-step work specifications and requirements before touching code, ensuring a clear roadmap and shared understanding.
Create a new plan by saving it to docs/plans/YYYY-MM-DD-<feature>.md and fill in the header, file map, and tasks.
High-intent search queries and answers about installing and using this skill.
To plan complex features before coding, outline your goals, architecture, and tech stack in a plan header, then define a file map and actionable task sequence saved to a standard markdown file path for team alignment.
Documenting multi-step requirements for refactoring involves creating a structured plan with a header capturing goals and architecture, a file map for modifications, and sequential actionable steps saved to a reusable markdown template.
Yes, you can use standard templates for feature development planning by saving plans to a fixed file path like docs/plans/YYYY-MM-DD-feature.md, enabling consistent documentation and reuse across multiple projects.
Yes, defining a file map is necessary when outlining requirements for a complex bug fix to explicitly enumerate files that need modification, ensuring precise task execution and clear documentation.
A development plan should include a header with goals, architecture, and tech stack, a file map detailing files to create or modify, and a sequence of actionable tasks to maintain shared understanding across teams.
Structured plans for task documentation are unnecessary for simple, single-step changes that do not require architecture outlines, file maps, or precise task sequencing to execute correctly.
xiaoweidotnetGenerate structured technical specification documents defining project scope, architecture, and success criteria.
beratcelik1Execute development plans into tasks, code changes, tests, and commits.
haidonglethqbCoordinate multi-plan project management by synchronizing Claude Tasks with plan files.
foyzulkarimTransforms feature plans into TDD task specifications with embedded test scenarios.
