Lotus Linear Init
Use this skill when a repository needs the Linear-backed Lotus rules.
Inspect First
- check whether
.local/AGENTS.md,.local/WORKFLOW.md, and.local/workflow.lotus.jsonalready exist - inspect current ignore rules for
.local/ - read root
AGENTS.mdwhen present for host repo constraints, but do not edit it unless the human explicitly asks - preserve existing project-specific Linear configuration when merging rules
Apply
- create
.local/AGENTS.mdfromassets/local-agents.mdwhen missing - when the file already exists, merge only the missing Linear-backed rules and preserve repo-specific constraints
- ensure
.local/is ignored via.git/info/exclude - do not create Linear issues, Linear documents, or external tickets during init
- keep active issue, progress, review, PR-note, and durable project state in Linear for this variant
- keep
.docs/AGENTS.mdand reusable.docstemplates available as durable agent guidance; they are not the operational Linear work state - local Lotus directories may exist only as private execution notes or
compatibility stores; they are not the operational source when
.local/workflow.lotus.jsonselectslinear-first
Required Local Configuration
Prefer .local/workflow.lotus.json for selected profiles, source priority,
source-of-truth modes, write permissions, and hygiene. Keep private
project-specific details in .local/WORKFLOW.md or .local/AGENTS.md, even
when the value is still a placeholder:
linear_team: <team-key-or-name>
linear_project: <project-name-or-id>
linear_flow_document: <document-title-or-id>
source_policy: <local-only|remote-read-through|remote-clone>
external_writes: disallowed-by-default
Operating Rules
- keep
.local/private and machine-local - keep all generated project and operational text in English
- use Linear as the operational and durable project source of truth after initialization
- write to external systems only after explicit human authorization for that target and action
Assets
assets/local-agents.md
Source: MrMaxie/lotus-agents — distributed by TomeVault.