writing-plans Skill
Use when design is complete and you need detailed implementation tasks for engineers with zero codebase context - creates comprehensive implementation plans with exact file paths, complete code examples, and verification steps assuming engineer has minimal domain knowledge Published by microsoft in FluidFramework.
What is writing-plans Skill?
Use when design is complete and you need detailed implementation tasks for engineers with zero codebase context - creates comprehensive implementation plans with exact file paths, complete code examples, and verification steps assuming engineer has minimal domain knowledge Published by microsoft in FluidFramework. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Testing
- Documentation
- Design and media
- Writing
- Testing use cases
Technical details
- Install or run with Copy skill directory
When to use writing-plans Skill
- Use it for testing.
- Use it for documentation.
- Use it for design and media.
- Use it for writing.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/FluidFramework
- Skill file: .agency/plugins/nori/skills/writing-plans/SKILL.md
What it does
Use when design is complete and you need detailed implementation tasks for engineers with zero codebase context - creates comprehensive implementation plans with exact file paths, complete code examples, and verification steps assuming engineer has minimal domain knowledge
Skill instructions
<required CRITICAL. Add the following steps to your Todo list using TodoWrite: - Read the 'Guidelines'. - Create a comprehensive plan that a senior engineer can follow. <system-reminderAny absolute paths in your plan MUST take into account any worktrees that may have been created</system-reminder - Think about backwards compability. Add any notes to the plan. - Think about edge cases. Add them to the plan. - Think about questions or areas that require clarity. Add them to the plan. - Emphasize how you will test your plan. - Present plan to user. </required Guidelines Overview Create a comprehensive implementation plans assuming the engineer has zero context for our codebase and questionable taste. Document everything they need to know: which files to touch for each task, code, testing, docs they might need to check, how to test it. Give them the whole plan as bite-sized tasks. DRY. YAGNI. TDD. Assume they are a talented developer. However, assume that they know almost nothing about our
Explore related resources
Frequently asked questions
What is writing-plans?
writing-plans is a open-source AI agent skill with Copy skill directory. Use when design is complete and you need detailed implementation tasks for engineers with zero codebase context - creates comprehensive implementation plans with exact file paths, complete code examples.
Who is writing-plans best for?
writing-plans is best for reusing agent instructions, scripts, and references, testing workflows, documentation workflows, design and media workflows.
How do I install writing-plans?
Install or run writing-plans using Copy skill directory. Check writing-plans for the latest setup command.
Is writing-plans actively maintained?
writing-plans may need a closer maintenance check before production use.
Auto-fetched from GitHub.
