openplan-docs-init

OpenPlan Docs Init

Use this after $openplan-core and usually after $openplan-align when a project needs an initial governed documentation surface before agents start generating durable docs.

Core Principle

Document generation begins with authority and provenance, not with a pile of files. Generated docs must not present agent assumptions as human intent.

When To Use

Use this skill when asked to:

• initialize an OpenPlan-style docs repo;
• add OpenPlan-style documentation governance to an existing code repo;
• create a minimal document map before generating project docs;
• seed needs snapshots, decision records, templates, or planning docs;
• prepare memory/docs for future Codex, Claude Code, or subagent sessions.

Do not use it for ordinary documentation edits after the document structure already exists. Use $openplan-record and $openplan-garden for that.

Init Flow

1. Identify the target surface:
   • docs repo;
   • code repo;
   • single-repo project;
   • temporary teaching/reporting surface.
2. Identify the documentation root:
   • explicit user-provided path;
   • existing project convention;
   • .openplan/ when docs should live inside a code repo without mixing with product docs;
   • docs/ or repo root when that is the project convention;
   • a separate docs repo or absolute path when provided.
3. Identify authority sources:
   • explicit human goal/intent;
   • existing docs/design/ADR files;
   • code evidence;
   • prior handoff or needs snapshot;
   • agent inference.
4. Decide the minimum document map needed for the next phase.
5. Before creating durable docs, state:
   • docs root;
   • what will be generated;
   • which source backs each file;
   • what is inferred or pending confirmation;
   • whether the file is source of truth, draft, handoff, review, or disposable.
6. Generate only the smallest useful scaffold unless the user explicitly asks for a broader docs package.
7. Record an explicit human decision, or propose/request a decision record, when initialization creates or changes durable design/governance.
8. Seed a needs snapshot when the human goal/intent or project direction must survive across agents or sessions.
9. Run $openplan-garden after broad generation and $openplan-record for durable memory/docs updates.
10. Use $openplan-research first when the docs scaffold depends on facts not already backed by local durable context.