본문으로 건너뛰기
cccskills
무료GitHub에 공개

docs-planner

Find the gaps in the Box documentation and produce a prioritized backlog for docs/user/ and docs/design/. Use when planning documentation work, after a feature or a binary ships without a page, for a periodic health check of the docs, or when asked "what docs need writing", "plan the docs work", "prioritize the docs backlog", or "what should we document next".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

strands-agents/box스타 475(GitHub 475 + cccskills 0)

실행 점수 미검증

설치 방법 보기

포함된 파일(1)

  • SKILL.md2.9 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Documentation planner

Find the gaps in the user guide and the design guide, and produce a backlog in priority order.

Inputs

  • Scope: all docs, one guide, or one area. The default is all docs.
  • Signals (optional): issues, questions from operators, or review findings.

Process

Step 1: Inventory

List each page in docs/user/ and docs/design/, and each crate README.md that serves a consumer. For each page, record its guide, its content type, and its area. Also read:

  • docs/README.md and the README.md of each guide, for the stated structure.
  • The "still to come" list in docs/design/README.md, for the planned design pages.

Step 2: Find the gaps

Compare the inventory with each of these:

  • The product surface. Each CLI verb, each box.toml top-level key, each process specification key, each filesystem list, the policy action vocabulary, and each binary that ships. A part of the surface with no page is a gap.
  • The content types. For each area, the user guide needs a how-to and a reference, and the design guide needs an explanation. An area with a reference and no how-to has a gap.
  • The premises in AGENTS.md. Each premise needs a design page that explains it to a security evaluator. A premise that only AGENTS.md explains is a gap.
  • Signals. If gh is available, read the open issues in the repository that mention docs. Map each to a page that is unclear or to a page that is missing.

Step 3: Prioritize

  • P0, do now. High impact, at any effort. Getting started, the architecture overview, and the security model.
  • P1, do soon. Medium impact, low effort. A how-to for a common task, or a reference for a surface that has none.
  • P2, plan for. Medium impact, high effort. An enforcement page, or the platform differences.
  • P3, backlog. Low impact. An edge case.

Step 4: Write the backlog

## Docs backlog: <scope>

**Date:** <date>
**Pages inventoried:** <count>
**Gaps found:** <count>

### P0: do now

- [ ] <Task>: <content type>, <target path>. <Reason.>

### P1: do soon

...

### Coverage

| Area | Tutorial | How-to | Reference | Explanation |
|---|---|---|---|---|
| Running a harness | Y | ~ | N | N |
| Filesystem grants | N | N | ~ | N |
| Binaries | N | N | N | N |

### From signals

- <A theme from the signals, and the gap that it maps to.>

Y is covered, ~ is partial, and N is missing.

What this skill does not do

  • Write a page. That is docs-writer.
  • Create issues or tasks in an external tool.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

authoring-box-policy

무료

Author or edit a Strands Box policy (`policy.dw`) — turn an operator's natural-language allow/deny intent into a validated Dogwood policy over the box's fixed action vocabulary, including `when temporal { … }` history rules. Use when writing, editing, reviewing, or converting an intent into a box policy. This skill CREATES or EDITS a policy against the box's built-in schema — you never author a Dogwood schema, because the box ships a fixed one.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

strands-agents/box4752026년 10월 26일 업데이트

debug-os-failure-on-github

무료

Debug a CI failure on an OS you are not on (you are on Linux, it fails on macos-latest, or the reverse) without opening a pull request per attempt. Use when a test is green on your machine and red on a GitHub runner, or when you need to run one test or one shell probe on a runner and read the result fast. The core move is a dispatchable, scoped workflow on your own fork: pick one OS, skip lint, filter to one test, and for environment questions run a no-build probe that returns in seconds instead of a ten-minute build. Iterate by pushing to the fork branch and re-dispatching, never by editing a PR.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

strands-agents/box4752026년 10월 26일 업데이트

docs-audit

무료

Assess an existing Box documentation page (docs/user/, docs/design/, or a crate README.md) for accuracy against the code and its tests, placement, and voice, and recommend what to fix. Use before a rewrite, when a page may have drifted from the code, or when asked to "audit this page", "is this page still true", or "what is wrong with this doc".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

strands-agents/box4752026년 10월 26일 업데이트

docs-reviewer

무료

Review a Box documentation draft in docs/user/ or docs/design/ for placement, structure, altitude, readability, terminology, and claim scope, and give a verdict (Ship it, Tighten, or Rethink). Use after docs-writer produces a draft, before a docs pull request, or when asked to "review this draft", "check my docs", or "is this page ready to ship". Read-only.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

strands-agents/box4752026년 10월 26일 업데이트

docs-writer

무료

Draft or rewrite a Box documentation page in docs/user/ (tutorial, how-to, or reference for an operator) or docs/design/ (explanation for a security evaluator or a contributor), or a crate README.md that serves a consumer. Use when asked to write a doc, draft a page, rewrite a page that failed audit, document a feature or a component, or write an architecture or security page. Not for docs/design/decisions.md (use kd), local specs (use spec), or research notes (use explore).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

strands-agents/box4752026년 10월 26일 업데이트

explore

무료

Launch a deep, multi-faceted investigation of a topic using parallel sub-agents. Each agent tackles a different angle simultaneously, and findings are synthesized into structured exploration documents.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

strands-agents/box4752026년 10월 26일 업데이트

strands-agents의 스킬 모두 보기

이 스킬의 문제 신고