無料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.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。

まだコメントはありません。最初のコメントを書いてみませんか。

同じリポジトリのスキル

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.

日本語の概要は準備中です。原文の説明を表示しています。