init

SkillAI & models

Set up docflow in a repo with no docs yet: scaffold the docs tree, write docflow.json, add agent guidance. Use when asked to "set up docflow", "initialize docs", "scaffold docs", or "make this repo use docflow".

Use init in Claude, ChatGPT or Ahel Desktop

Free. Sign in, add init and connect your AI. About a minute.

Also: Claude Code · Cursor · Codex

Then ask your AI: use the init skill

Details

Instructions available. Your AI can read the instructions. Execution depends on the setup they require.

Add Ahel to your AI once: Claude, ChatGPT, Cursor, Claude Code or Codex. Then ask it to use this.

What this skill tells your AI

The instructions your AI receives, as published by hashgraph-online/awesome-codex-plugins in plugins/MedAdemBHA/docflow/skills/init/SKILL.md and read by Ahel’s review.

Goal: initialize docflow only when doctor says this repo has no meaningful docs yet. Keep existing user-authored files; generated maintenance files may be refreshed.

Steps

  1. Run doctor first.
bash scripts/docflow-doctor.sh --target <REPO ROOT>
  1. Route by recommendation.

    • docflow-init: continue.
    • docflow-adopt: stop and run /docflow:adopt instead (preserves existing docs).
    • docflow-repair: stop and run /docflow:repair instead.
  2. Pick docs root.

    • Use docs/ unless the user explicitly chooses another root.
  3. Pick project name.

    • Prefer repo folder name.
    • If root README.md has clear project title, use that.
  4. Run scaffold from plugin root (idempotent; skips existing user content, refreshes generated files):

bash scripts/scaffold.sh --docs-root <DOCS_ROOT> --project "<PROJECT NAME>" --target "<REPO ROOT>"

This creates the category tree, drops templates, writes docflow.json, and scaffolds AGENTS.md + GEMINI.md + .cursorrules.

  1. Add root README link if missing:

    • ## Documentation
    • link to <DOCS_ROOT>/README.md
  2. Seed the first changelog. Create <DOCS_ROOT>/changelog/(mmm-yy).md for the current month from the template, summarizing recent history (git log --no-merges --pretty='%h %ad %s' --date=short -20). Use the changelog skill for the format.

  3. Regenerate the map and validate:

    bash scripts/docflow-map.sh "<REPO ROOT>/<DOCS_ROOT>"
    bash scripts/docflow-validate.sh --target "<REPO ROOT>"
    

    Fresh template placeholders are warnings; validation errors are blockers.

  4. Report what was created (docs root, docflow.json, AGENTS.md, GEMINI.md, .cursorrules, validation status) and point the user at /docflow:author (writing), /docflow:router (reading), /docflow:validate (readiness), /docflow:repair (maintenance).

Rules

  • Never overwrite existing user-authored docs files.
  • If docs already exist, prefer /docflow:adopt over /docflow:init.
  • Keep AGENTS.md and docflow.json aligned on docs root.
  • Follow the naming rules in <DOCS_ROOT>/NAMING.md for every file you create after.

Signals

GitHub stars
1k
Forks
316
Last commit
Oct 2026
Advanced
Item type
skill
Key
init-hashgraph-online
Source
github.com/hashgraph-online/awesome-codex-plugins