Menú
Bootstrap or merge a .planning/ setup from existing ADRs, PRDs, SPECs, and docs in a repo.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, update or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
Use this skill when the user wants direct operations on an Obsidian vault: read or edit notes and daily notes, search vault contents, count or list notes, manage tasks, move or rename files, find orphaned notes or broken links, inspect frontmatter/properties, manage sync or file history, query Bases, manage bookmarks, script the CLI, or run JavaScript against the Obsidian API. Trigger when the request implies "go into my vault and do X"; the user wants action on vault data, not an explanation. Skip pure conceptual or GUI-help questions such as settings navigation, theme/plugin installation, sync troubleshooting, Dataview syntax, keyboard shortcuts, or parsing vault files with unrelated external scripts.
Captures corrections, failures, missing capabilities, and reusable discoveries in agent so future work improves. Use this skill whenever a command, tool, or API fails unexpectedly; the user corrects the agent; the agent realizes its knowledge is outdated or wrong; a missing capability is exposed; or a better recurring approach is discovered. Record the result under .agents/learnings/, review related entries before major tasks, and promote durable workflow rules into AGENTS.md when they should change future behavior.
Generate tests for a completed phase based on UAT criteria and implementation
Generate an AI-SPEC.md design contract for phases that involve building AI systems.
Autonomous audit-to-fix pipeline — find issues, classify, fix, test, commit
| name | gsd-ingest-docs |
| description | Bootstrap or merge a .planning/ setup from existing ADRs, PRDs, SPECs, and docs in a repo. |
--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.--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.
<execution_context> @/home/aming/.config/opencode/gsd-core/workflows/ingest-docs.md @/home/aming/.config/opencode/gsd-core/references/ui-brand.md @/home/aming/.config/opencode/gsd-core/references/gate-prompts.md @/home/aming/.config/opencode/gsd-core/references/doc-conflict-engine.md </execution_context>
$ARGUMENTS Execute the ingest-docs workflow end-to-end. Preserve all approval gates (discovery, conflict report, routing) and the BLOCKER safety rule.