using-docpowers
Use when creating, repairing, auditing, or organizing documentation for repositories, packages, skills, packs, APIs, or mathematical projects.
- License 许可
- GPL-3.0
- 最近更新
- 2026-11-13
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- using-docpowers
- description
- Use when creating, repairing, auditing, or organizing documentation for repositories, packages, skills, packs, APIs, or mathematical projects.
02 资源文件 2
- 参考文档references/documentation-contract.md1.4 KB
- 参考文档SPEC.md1.5 KB
03 SKILL.md 正文
Invoke using-superpowers once and reuse the active coordinator. Read
references/documentation-contract.md. Preserve existing specialized routes;
choose one primary leaf from observable evidence, then compose a test leaf only
for executable examples. Never recursively invoke using-testpowers.
| Evidence in the request or repository | Primary route |
|---|---|
| Read-only Mathcity policy audit; Mathcity documentation edit; Magma/Sage package README edit | check-documentation-policy; improve-documentation; improve-package-README |
| Sage, M2, Magma, Lean, or LaTeX layout/toolchain | doc-math-sage, doc-math-m2, doc-math-magma, doc-math-lean, or doc-math-latex |
| Gas City pack, manifest, generated index, or source registry | doc-pack-gascity |
| Claude/Codex skill collection or plugin bundle | doc-pack-skills |
| Pack/plugin/package/bundle documentation | doc-pack |
| Install, acquisition, configuration, or first useful command | doc-quickstart |
| Worked example, tutorial, doctest, or executable snippet | doc-examples |
| Public API, declaration, method, command, or error contract | doc-api |
| Links, index, parent page, orphan, or canonical-home issue | doc-navigation |
| Citation, attribution, license, date, status, limitation, or roadmap | doc-provenance |
| Repository-wide creation or repair | doc-repository |
| Read-only quality/completeness/freshness audit | doc-assess |
For mixed requests, document first and name the test handoff explicitly. Return changed paths or findings, commands/results, unresolved gaps, and unavailable toolchains. Keep routers thin and leave detailed procedure to leaves.
04 同仓库更多 Skills
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
using-superpowers
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code