inits
Init - AGENTS.md Generator
Analyze this codebase and create or improve an AGENTS.md file for future ODIN Code Agent instances.
Core principle
Only encode knowledge that is expensive to rediscover. An agent can fd, rg, ast-grep, and read files in seconds. If the information is one search away, omit it.
Objective guard
AGENTS.md is for priming and guiding future agents with conventions, constraints, and rationale. It is not a repository summary.
What to include
- Cross-cutting conventions and boundaries that span multiple files.
- Implicit contracts and operational constraints that are easy to miss in quick code exploration.
- Non-obvious command guidance only when hidden constraints matter (required ordering, flags, env vars, caveats).
- For each included item, state:
- the rule or constraint
- why it exists (rationale)
What to omit (the agent can discover these)
- File trees, per-directory descriptions, or component inventories.
- Dependency/version tables.
- Generic development best practices.
- Information that is easily discoverable via search/read.
- Fabricated filler sections such as "Common Development Tasks", "Tips", or "Support".
- Any summary-style prose that restates code organization without conventions or rationale.
Workflow
- If
AGENTS.mdalready exists, suggest targeted improvements instead of rewriting. - Do not repeat yourself. Each fact appears once.
- Every statement must be grounded in files you actually read. Never invent.
- If uncertain, omit the claim rather than speculate.
More from outlinedriven/odin-claude-plugin
ast-grep
Effective code search, analysis, and refactoring using ast-grep (sg). Use this skill for precise AST-based code modifications, structural search, and linting.
2proceed
Execute an implementation plan with surgical precision. Use after a planning phase (plan-now or similar) has produced a step-by-step strategy and identified critical files. Focuses on precise code changes with verification at each step.
1askme
Verbalized Sampling (VS) protocol for deep intent exploration before planning. Use when starting ambiguous or complex tasks, when multiple interpretations exist, or when you need to explore diverse intent hypotheses and ask maximum clarifying questions before committing to an approach.
1plans
Software architect and planning specialist - conduct thorough read-only planning before any action. Use when exploring a codebase to design implementation plans, defining objectives, gathering relevant files, and summarizing available tools before coding begins.
1reviews
Review the code changes on the current branch. Use when the user asks to review their current work, analyze recent commits, or get a code quality assessment of the active branch against the main branch.
1resolve
Resolve code review comments by verifying their validity and proposing multiple solutions for confirmed issues. Use when addressing review feedback, analyzing whether review comments are valid, and generating architectural solutions (not naive fixes) for confirmed issues.
1