Agent skill

Agentic Doc Ingest

by PackmindHub in PackmindHub/packmind

Turn the charter, decision log and unit records of a completed feature into documentation — user-facing guides or technical notes — without reading the implementation.

Apache-2.0Auto-check passedDevelopment

Install Agentic Doc Ingest

skills CLI
$ npx skills add PackmindHub/packmind --skill agentic-doc-ingest -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install PackmindHub/packmind agentic-doc-ingest --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/PackmindHub/packmind.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/agentic-doc-ingest .claude/skills/agentic-doc-ingest && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
agentic-doc-ingest
GitHub stars
317
Token cost
~755 tokens
SKILL.md length
360 words
Files
1
Skills in repo
35
Repo updated
First seen
Licence
Apache-2.0

At a glance

Turn the charter, decision log and unit records of a completed feature into documentation — user-facing guides or technical notes — without reading the implementation.

  • A feature built through the agentic development pipeline is finished and needs documenting
  • SKILL.md covers Why you do not read the code, Why the decision log alone is…, The two documents are not the… and The coverage check, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • The user says document that feature

What it does

Agentic Doc Ingest is an agent skill from PackmindHub/packmind. Turn the charter, decision log and unit records of a completed feature into documentation — user-facing guides or technical notes — without reading the implementation. Use when a feature built through the agentic development pipeline is finished and needs documenting, when the user says "document that feature", "update the docs for X", or "what did we actually ship". Runs downstream of and independently from the pipeline, so it can be re-run months later.

Its SKILL.md is about 760 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Architecture decision records. The repository describes itself as: Packmind seamlessly captures your engineering playbook and turns it into AI context, guardrails, and governance. The licence is Apache-2.0.

When your agent uses it

  • A feature built through the agentic development pipeline is finished and needs documenting
  • The user says document that feature
  • Update the docs for X
  • What did we actually ship

Example prompts

  • “document that feature”
  • “update the docs for X”
  • “what did we actually ship”
  • “/agentic-doc-ingest”

What it can do on your machine

Read from SKILL.md and the folder at commit 8a10541. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Agentic Doc Ingest loads about 755 tokens when it runs. Until then it costs about 120 tokens; SKILL.md has 360 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~120
When it runs · the whole SKILL.md, loaded when a task matches
~755

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from PackmindHub/packmind at commit 8a10541, republished under its Apache-2.0 licence (© PackmindHub). 360 words, ~755 tokens.

Download SKILL.mdSave it as .claude/skills/agentic-doc-ingest/SKILL.md (or your agent's skills folder).
name
agentic-doc-ingest
description
Turn the charter, decision log and unit records of a completed feature into documentation — user-facing guides or technical notes — without reading the implementation. Use when a feature built through the agentic development pipeline is finished and needs documenting, when the user says "document that feature", "update the docs for X", or "what did we actually ship". Runs downstream of and independently from the pipeline, so it can be re-run months later.

Documentation ingest

You write documentation from three files and no code:

.claude/features/<slug>/charter.md      what was meant to be built, and for whom
.claude/features/<slug>/decisions.md    what was decided, and what was rejected
.claude/features/<slug>/records.jsonl   what each unit actually did

Why you do not read the code

Because you do not have to, and that is deliberate. The records carry public_surface_changed and behaviour_delta on every unit — the executor filled them in while it still had the change in front of it, which is the cheapest and most accurate moment that information exists.

Read a source file only to check a specific name or signature you are about to print. Not to survey, not to "understand the feature".

Why the decision log alone is not enough

The decision log records intent. Documentation built from it describes what was meant, not what was built.

The deviations field across the records is exactly that gap. Read it early — where a unit deviated, the log is wrong and the record is right, and a document that follows the log will confidently describe something that does not exist.

The two documents are not the same document

Decide which you were asked for; do not blend them.

User-facing. Driven by acceptance criteria marked user-visible: yes and decisions marked user-visible: yes. Task-oriented, no implementation detail. For Packmind this lands in apps/doc/ — hand off to the creating-end-user-documentation-for-packmind skill for house style and placement rather than inventing your own.

Technical. Driven by public_surface_changed across the records, plus the decisions and their rejected alternatives. Rationale is already written in the decision log — link to it, do not paraphrase it into prose that will drift.

Show full SKILL.md (115 more words)Show less

The coverage check

Before you finish, verify: every entry marked user-visible: yes, in both the charter and the decision log, has a corresponding mention in what you wrote.

List the ones that do not, and say why you left them out. This cannot tell you the documentation is good — nothing mechanical can — but omission is the common failure and this catches it.

Output

Write the files. Do not commit them.

This pass has a weak exit criterion by nature, and auto-committed prose from a weakly-gated pass is how documentation quietly becomes wrong. Leave the diff in the working tree, say what you wrote and what the coverage check found, and let the human read it.

© PackmindHub, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/agentic-doc-ingest of PackmindHub/packmind.

Open the folder on GitHubat commit 8a10541

Compare with similar skills

Agentic Doc Ingest next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Agentic Doc Ingest compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Agentic Doc Ingest this skillPackmindHub/packmind317—~755Automated safety check: PassApache-2.0
PR Design DocOpenHands/OpenHands90k—~2.4kAutomated safety check: PassMIT
Cto AdvisorIbrahim-3d/orchestrator-supaconductor3804 repos~2.4kAutomated safety check: PassMIT
Improve Codebase Architectureywwynm/EverythingDone14415 repos~1.3kAutomated safety check: PassGPL-3.0
Domain Modelingbrim-borium/spotify_sdk1665 repos~806Automated safety check: PassApache-2.0
Design Doc MermaidSpillwaveSolutions/design-doc-mermaid1751 repos~5.6kAutomated safety check: PassNone

Similar skills

  • PR Design Doc

    OpenHands/OpenHands

    For a non-trivial pull request, write a self-contained HTML design doc under the temporary .pr/ directory and link a visibility-appropriate preview in the PR description, so maintainers grasp the…

    90k GitHub stars~2.4k tokensUpdated today
    DevelopmentAuto-check passed
  • Cto Advisor

    Ibrahim-3d/orchestrator-supaconductor

    Technical leadership guidance for engineering teams, architecture decisions, and technology strategy.

    380 GitHub starsUsed in 4 repos~2.4k tokens
    DevelopmentAuto-check passed
  • Improve Codebase Architecture

    ywwynm/EverythingDone

    Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/.

    144 GitHub starsUsed in 15 repos~1.3k tokens
    DevelopmentAuto-check passed
  • Domain Modeling

    brim-borium/spotify_sdk

    Build and sharpen a project's domain model. An agent skill from brim-borium/spotify_sdk.

    166 GitHub starsUsed in 5 repos~806 tokens
    DevelopmentAuto-check passed
  • Design Doc Mermaid

    SpillwaveSolutions/design-doc-mermaid

    Create Mermaid diagrams (flowchart, sequence, class, ER, state, C4, architecture) from text or source code.

    175 GitHub starsUsed in 1 repo~5.6k tokens
    DevelopmentAuto-check passed
  • Learning Opportunities

    DrCatHicks/learning-opportunities

    Facilitates deliberate skill development during AI-assisted coding.

    2.5k GitHub stars~2.5k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed

More from PackmindHub/packmind

All 35 skills in this repo
  • Michel CLI Demo Recorder

    PackmindHub/packmind

    Produce proof-of-execution demos of the Packmind CLI (packmind-cli) as terminal-styled images (colors and formatting preserved exactly), for embedding in a GitHub PR.

    317 GitHub stars~3.4k tokensUpdated today
    Auto-check passed
  • Michel UI Demo Recorder

    PackmindHub/packmind

    Record polished UI demo videos and screenshots of a running web app using Playwright MCP — for client deliverables, release notes, feature walkthroughs, or bug repros.

    317 GitHub stars~6.4k tokensUpdated today
    Auto-check passed
  • Packmind Create Skill

    PackmindHub/packmind

    Guide for creating effective skills. An agent skill from PackmindHub/packmind.

    317 GitHub stars~3.5k tokensUpdated today
    Auto-check: notes
  • Doc Audit

    PackmindHub/packmind

    Audit Packmind end-user documentation (apps/doc/) for broken links, outdated CLI references, non-existent concepts, misleading information, and missing coverage.

    317 GitHub stars~2.4k tokensUpdated today
    Auto-check passed
  • Feature Sprint

    PackmindHub/packmind

    Execute the implementation plan produced by /feature-spec. An agent skill from PackmindHub/packmind.

    317 GitHub stars~1.9k tokensUpdated today
    Auto-check passed
  • Review an implemented GitHub issue the way a senior Packmind engineer would — the human-judgment checks that ESLint, the TypeScript compiler, and e2e tests cannot catch (authorization scoping…

    317 GitHub stars~2.7k tokensUpdated today
    Auto-check passed

Categories

Questions about Agentic Doc Ingest

What does Agentic Doc Ingest do?

Turn the charter, decision log and unit records of a completed feature into documentation — user-facing guides or technical notes — without reading the implementation. Agentic Doc Ingest is an agent skill from PackmindHub/packmind. Turn the charter, decision log and unit records of a completed feature into documentation — user-facing guides or technical notes — without reading the implementation.

When should I use Agentic Doc Ingest?

Agentic Doc Ingest fits situations like: A feature built through the agentic development pipeline is finished and needs documenting; the user says document that feature; update the docs for X; what did we actually ship.

How do I install Agentic Doc Ingest in Claude Code?

Run `npx skills add PackmindHub/packmind --skill agentic-doc-ingest -a claude-code`. Or copy the skill folder (.claude/skills/agentic-doc-ingest in PackmindHub/packmind) into .claude/skills/agentic-doc-ingest in your project. Claude Code loads it when a task matches its description.

How do I install Agentic Doc Ingest in Codex?

Run `npx skills add PackmindHub/packmind --skill agentic-doc-ingest -a codex`. Or copy the skill folder (.claude/skills/agentic-doc-ingest in PackmindHub/packmind) into .agents/skills/agentic-doc-ingest in your project. Codex loads it when a task matches its description.

Can I use Agentic Doc Ingest in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add PackmindHub/packmind --skill agentic-doc-ingest -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/agentic-doc-ingest, .gemini/skills/agentic-doc-ingest, .github/skills/agentic-doc-ingest and .opencode/skills/agentic-doc-ingest in your project.

What does Agentic Doc Ingest need to run?

SKILL.md names no scripts, command-line tools or credentials: Agentic Doc Ingest is instructions for the agent only.

Does Agentic Doc Ingest access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Agentic Doc Ingest safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Agentic Doc Ingest use?

Agentic Doc Ingest is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Agentic Doc Ingest use?

About 755 tokens (SKILL.md is roughly 3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Agentic Doc Ingest?

Skills that share tags, products or a category with Agentic Doc Ingest: PR Design Doc (OpenHands/OpenHands, 90k stars), Cto Advisor (Ibrahim-3d/orchestrator-supaconductor, 380 stars), Improve Codebase Architecture (ywwynm/EverythingDone, 144 stars) and Domain Modeling (brim-borium/spotify_sdk, 166 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Agentic Doc Ingest?

PackmindHub (a GitHub organization) maintains it in PackmindHub/packmind, which has 317 GitHub stars. The repository holds 35 skills in this directory. The repository was last updated on October 8, 2026.

Source: PackmindHub/packmind on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.