task-planning Skill
Turn a Paperclip issue or request into a structured implementation plan with child task graph, blockers, owners, and acceptance criteria, then save it as the issue plan document. Published by microsoft in amplifier-app-paperclip.
What is task-planning Skill?
Turn a Paperclip issue or request into a structured implementation plan with child task graph, blockers, owners, and acceptance criteria, then save it as the issue plan document. Published by microsoft in amplifier-app-paperclip. 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
- Documentation
- Design and media
- Documentation use cases
- Design and media use cases
Technical details
- Install or run with Copy skill directory
When to use task-planning Skill
- Use it for documentation.
- Use it for design and media.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/amplifier-app-paperclip
- Skill file: packages/skills-catalog/catalog/bundled/paperclip-operations/task-planning/SKILL.md
What it does
Turn a Paperclip issue or request into a structured implementation plan with child task graph, blockers, owners, and acceptance criteria, then save it as the issue plan document.
Skill instructions
Task Planning Produce implementation plans that the Paperclip executor can actually run: explicit child issues, real blockers, named owners, and a defined acceptance bar. Avoid plans that read well but cannot be split into work. When to use - An issue asks you to "plan", "scope", "break down", "design the rollout", "propose the work", or similar. - A user wants a written plan before approving implementation. - A manager needs to delegate non-trivial work and the shape of the work is not obvious yet. - You inherited an issue too large to deliver in one heartbeat and need to split it. When not to use - The issue is a single small change you can ship in the same heartbeat. Just ship it. - The issue is forensic ("why did this break"). Use a diagnosis skill first; plan only after the root cause is named. - A current plan document already exists and the change is minor. Update that document; do not start fresh. Outputs 1. An updated issue document with key plan (markdown). 2. A short comment
Explore related resources
Frequently asked questions
What is task-planning?
task-planning is a open-source AI agent skill with Copy skill directory. Turn a Paperclip issue or request into a structured implementation plan with child task graph, blockers, owners, and acceptance criteria, then save it as the issue plan document.
Who is task-planning best for?
task-planning is best for reusing agent instructions, scripts, and references, documentation workflows, design and media workflows.
How do I install task-planning?
Install or run task-planning using Copy skill directory. Check task-planning for the latest setup command.
Is task-planning actively maintained?
task-planning may need a closer maintenance check before production use.
Auto-fetched from GitHub.
