handle-large-tasks
Use this skill to split large plans into smaller chunks. This skill manages your context window for large tasks. Use it when a task will take a long time and cause context issues.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 4.9k
- Forks
- 590
01 前言 Front Matter
- name
- handle-large-tasks
- description
- Use this skill to split large plans into smaller chunks. This skill manages your context window for large tasks. Use it when a task will take a long time and cause context issues.
02 资源文件 1
- 参考文档references/attribution.md1.9 KB
03 SKILL.md 正文
<required> CRITICAL Add the following steps to your Todo list using TodoWrite:
- Announce that you are creating subagents.
- Construct a plan for each subagent.
- Write a test for each subagent based on what you expect the subagent to do.
- Start each subagent using the Task tool with instructions to make the test pass.
- Subagents may come back and ask questions or present plans. Review and provide feedback.
- You may have to restart subagents. If that happens, simply pass in the previous produced plan.
- Evaluate the code the subagent produces. Give feedback. Iterate until tests pass AND the code fits.
- When all subagents complete, make sure all tests pass and all of the code fits together coherently. </required>
Guidelines
Use subagents to manage your context. Each subagent has its own limited context window. Subagents perform best when they have clear implementation guidelines. Each subagent should be given a small and precise task. Create tests for each subagent and explicitly tell the subagent that it is responsible for making sure that test passes. The tests should test behavior. You are responsible for the final output. That means you MUST ensure that everything runs as expected. You should create high level tests that validate overall behavior.
04 同仓库更多 Skills
trigger-pipelines-for-copilot-pr
Trigger ADO pipelines for a Copilot-created PR by posting /azp run comments. Use when the user asks to trigger CI pipelines for a specific PR.
review
Review changes relative to a prior state, such as a diff, pull request, branch, commit, or working-tree changes. Use for change-focused code review and regression analysis. Do not use to assess an existing file, API, design, implementation, or other artifact without a comparison; if the request is ambiguous, ask whether the user wants a change review and what prior state to compare against.
review-pr-local
The authority on pulling a pull request — Azure DevOps or GitHub — into an isolated local worktree so a human can review it in their editor, and on posting human-controlled review comments back to the PR (ADO via the ado PR-thread MCP tools or the Azure DevOps REST API, GitHub via the gh CLI). Auto-detects the platform and all identifiers from the PR URL; not tied to any specific repository. The AI assists an interactive human review and only ever posts comments the human explicitly requests. If you find yourself checking out a PR branch over the user's own working tree, or posting AI-authored review prose the human did not ask for, invoke this skill instead.
policy-check
This skill should be used when the user asks to "run policy check", "check policy", "policy-check", or needs to validate package compliance. Provides guidance on running policy checks for specific packages or the entire repository.
pipeline-test-triage
Triage test failures in an Azure DevOps pipeline run for Fluid Framework. Use when the user shares an ADO build/pipeline URL or build ID and wants failures analyzed, when they ask "why did this pipeline fail", "summarize the test failures", "is this test flaky or a real bug", "compare these runs", or wants bugs filed for genuine failures. Covers the Real Service End to End Tests pipeline as the worked example but applies to any FF test pipeline.
fluid-release
Fluid Framework client release group — minor releases, patch releases, and post-release type test updates. Covers release prep, branching, version bumps, changelogs, release notes, and type test baselines. In autonomous mode, auto-detects state from the repo, attempts to execute, and falls back to a GitHub issue on failure. Triggers on "release", "do the release", "release status", version bump, release notes, changelog, release branch, or release engineering.