Lotus Init

Lotus Init

Use this skill when a repository needs the base Lotus setup.

Inspect First

1. check whether these already exist:
   • .local/AGENTS.md
   • .local/issues/
   • .local/issues-notes/
   • .local/reviews/
   • .local/pr-notes/
   • .local/WORKFLOW.md
   • .local/workflow.lotus.json
   • .docs/AGENTS.md
   • .docs/spec/
   • .docs/meetings/
   • .docs/templates/
   • .docs/practices/
2. check current ignore rules for .local/ and .docs/
3. inspect whether the repository looks mature or still bootstrap-only:
   • mature: substantial existing product code, signs of ongoing maintenance, or a repo that has clearly lived for a while
   • early: very few files, mostly example or starter code, or almost no real product code yet
4. read root AGENTS.md when present for host repo constraints, but do not edit it unless the human explicitly asks

Apply

• create the minimal missing base structure:
  • .local/AGENTS.md from assets/local-agents.md
  • .local/issues/ with .local/issues/.lotus.json from assets/local-issues.lotus.json
  • .local/issues-notes/ with .local/issues-notes/.lotus.json from assets/local-issues-notes.lotus.json
  • .local/reviews/ with .local/reviews/.lotus.json from assets/local-reviews.lotus.json
  • .local/pr-notes/ with .local/pr-notes/.lotus.json from assets/local-pr-notes.lotus.json
  • .local/WORKFLOW.md from assets/local-workflow.md
  • .local/workflow.lotus.json from the CLI-generated workflow config when profile or task-source choices are known
  • .docs/AGENTS.md from assets/docs-agents.md
  • .docs/spec/ with .docs/spec/.lotus.json from assets/docs-spec.lotus.json
  • .docs/meetings/_draft.md from assets/meetings-draft-template.md
  • .docs/templates/ with .docs/templates/.lotus.json from assets/docs-templates.lotus.json
• create .docs/practices/ only when the user wants practice files or wants the fuller starter shape
• when .local/AGENTS.md or .docs/AGENTS.md already exists, merge only the missing Lotus rules and preserve repo-specific constraints

Ignore Rules

• ensure .local/ is ignored via .git/info/exclude
• if the user has already said whether .docs/ should stay committed or local-only, follow that
• if the repo already has meaningful code and the agent can ask a short clarifying question, ask which version the human prefers
• if the repo already has meaningful code and the agent cannot ask or should not block on the question, default to hidden .docs/:
  • keep .docs/ local-only
  • ensure .docs/ is ignored via .git/info/exclude
  • mention that the human can ask to unhide or commit .docs/ later
• if the repo is still early, mostly bootstrap, example-heavy, or almost empty, default to committed .docs/:
  • do not ignore .docs/
  • mention that the human can ask to hide .docs/ later

Operating Rules

• do not create or update root AGENTS.md as part of Lotus setup unless the human explicitly asks
• do not create AGENTS_TO_COPY.md or AGENTS_ISSUE_FLOW.md
• do not create .local/context.md, .local/questions/, or .local/runs/
• keep the setup minimal when the repo already has part of the structure

Assets

• assets/local-agents.md
• assets/docs-agents.md
• assets/meetings-draft-template.md
• assets/local-issues.lotus.json
• assets/local-issues-notes.lotus.json
• assets/local-reviews.lotus.json
• assets/local-pr-notes.lotus.json
• assets/local-workflow.md
• assets/docs-spec.lotus.json
• assets/docs-templates.lotus.json

Source: MrMaxie/lotus-agents — distributed by TomeVault.