knownstaskreopen
Use when reopening a completed task to add new requirements, fix issues, or extend functionality
Use when reopening a completed task to add new requirements, fix issues, or extend functionality
Executes implementation plans with smart task grouping. Groups related tasks to share context, parallelizes across independent subsystems.
Create implementation plans with tasks grouped by subsystem. Related tasks share agent context; groups parallelize across subsystems.
Use when updating, versioning, deprecating, or maintaining existing Standard Operating Procedures. Covers keeping SOPs accurate, relevant, and synchronized with implementation changes.
Use when responding to production incidents following SRE principles and best practices.
Use when creating structured operational runbooks for human operators. Covers runbook organization, documentation patterns, and best practices for clear operational procedures.
Use when structuring Standard Operating Procedures with proper sections, organization, and markdown formatting. Covers SOP anatomy and section organization.
Use when defining and configuring Mise tasks in mise.toml. Covers task definitions, dependencies, file tasks, and parallel execution.
Use when creating incident response procedures and on-call playbooks. Covers incident management, communication protocols, and post-mortem documentation.
Complete budgeting and forecasting workflow covering annual budgets, departmental budgets, rolling forecasts, and variance analysis. Delivers documented budgets with approval trails.
Portfolio-level risk management skill for identifying, assessing, and mitigating risks across multiple projects. Maintains RAID logs and tracks risk responses.
Strategic portfolio planning skill for multi-project coordination, capacity assessment, and portfolio optimization. Provides framework for portfolio-level decision making.
Four-phase debugging framework - root cause investigation, pattern analysis, hypothesis testing, implementation. Ensures understanding before attempting fixes.
Structured workflow for production incident management following SRE best practices. Covers incident declaration, triage, coordination, resolution, and post-mortem.
Resource capacity planning and allocation skill for managing people and skills across multiple projects. Identifies conflicts, gaps, and optimization opportunities.
Controlled plan execution with human review checkpoints - loads plan, executes in batches, pauses for feedback. Supports one-go (autonomous) or batch modes.
Structured workflow for infrastructure migration planning including cloud migrations, technology upgrades, and data center transitions.
Structured workflow for infrastructure capacity planning including growth forecasting, scaling strategy, and resource provisioning decisions.
5 specialist PMO agents for portfolio management, resource planning, governance, risk analysis, and executive reporting. Dispatch when you need portfolio-level oversight.
Merge/simplify an over-fragmented outline to hit a paper-like section budget (NO PROSE): target final ToC ~6–8 H2, fewer thicker H3. **Trigger**: outline budget, merge sections, too many sections, H3 explosion, 大纲预算, 合并小节, 大纲太碎. **Use when**: `outline/outline.yml` exists but would produce thin sections (too many H2/H3); before (or immediately after) `section-mapper`. **Skip if**: outline is already within budget and approved; or you are already drafting prose. **Network**: none. **Guardrail**: NO PROSE; do not invent new topics; keep scope consistent; if you change section ids, you must reset mapping.
Select the most appropriate pipeline for a user goal, lock it in `PIPELINE.lock.md`, and route checkpoint questions into `DECISIONS.md`. **Trigger**: pipeline router, choose pipeline, workflow selection, PIPELINE.lock.md, 选择流程. **Use when**: 用户目标/交付物不清晰,需要在 snapshot/survey/tutorial/systematic-review/peer-review 中选一个并设置最小 HITL 问题集。 **Skip if**: pipeline 已锁定(`PIPELINE.lock.md` 存在)且所需问题已回答/签字完成。 **Network**: none. **Guardrail**: 尽量一次性提问;信息不足就写 `DECISIONS.md` 并停下等待。
Planner-pass coverage + redundancy report for an outline+mapping, producing `outline/coverage_report.md` and `outline/outline_state.jsonl`. **Trigger**: planner, dynamic outline, outline refinement, coverage report, 大纲迭代, 覆盖率报告. **Use when**: you have `outline/outline.yml` + `outline/mapping.tsv` and want a verifiable, NO-PROSE planner pass before writing. **Skip if**: you don't want any outline/mapping diagnostics (or you have a frozen/approved structure and will not change it). **Network**: none. **Guardrail**: NO PROSE; do not invent papers; only report coverage/reuse and propose structural actions as bullets.
Dashboard pattern for tracking doc coverage across product versions, locales, and channels.
Framework for capturing documentation requirements, scoring priority, and assigning owners.