agentleFS
adrianoanthonymma16-boopadrianoanthonymma16-boop/opencode-agents/skills/gsd-ingest-docs/SKILL.md

gsd-ingest-docs

Skill1 starsChanged 57 days agoMITView on GitHub

Bootstrap or merge a .planning/ setup from existing ADRs, PRDs, SPECs, and docs in a repo.

4 other projects use a version of this, 4 of them edited.

Adopted by

Most recently taken up by

The file

Files
SKILL.md
<objective> Build the full `.planning/` setup (or merge into an existing one) from multiple pre-existing planning documents — ADRs, PRDs, SPECs, DOCs — in one pass.
  • Net-new bootstrap (--mode new, default when .planning/ is absent): produces PROJECT.md + REQUIREMENTS.md + ROADMAP.md + STATE.md from synthesized doc content, delegating final generation to gsd-roadmapper.
  • Merge into existing (--mode merge, default when .planning/ is present): appends phases and requirements derived from the ingested docs; hard-blocks any contradiction with existing locked decisions.

Auto-synthesizes most conflicts using the precedence rule ADR > SPEC > PRD > DOC (overridable via manifest). Surfaces unresolved cases in .planning/INGEST-CONFLICTS.md with three buckets: auto-resolved, competing-variants, unresolved-blockers. The BLOCKER gate from the shared conflict engine prevents any destination file from being written when unresolved contradictions exist.

Inputs: directory-convention discovery (docs/adr/, docs/prd/, docs/specs/, docs/rfc/, root-level {ADR,PRD,SPEC,RFC}-*.md), or an explicit --manifest <file> YAML listing {path, type, precedence?} per doc.

v1 constraints: hard cap of 50 docs per invocation; --resolve interactive is reserved for a future release. </objective>

<execution_context> @/home/tony/.config/opencode/gsd-core/workflows/ingest-docs.md @/home/tony/.config/opencode/gsd-core/references/ui-brand.md @/home/tony/.config/opencode/gsd-core/references/gate-prompts.md @/home/tony/.config/opencode/gsd-core/references/doc-conflict-engine.md </execution_context>

<context> $ARGUMENTS </context><process> Execute the ingest-docs workflow end-to-end. Preserve all approval gates (discovery, conflict report, routing) and the BLOCKER safety rule. </process>

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.