Repository navigation
feat(aidd-context): add Kilo support and correct OpenCode rule guidance #788
Description
Problem
aidd-context generators must match the current artifact contracts of the selected host tools. The OpenCode rule reference currently claims a native .opencode/rules/ surface that OpenCode does not document. Kilo is absent from the relevant detection and generation references.
Scope
- Correct OpenCode rule guidance: offer
AGENTS.mdor a Markdown file referenced fromopencode.json[c].instructions, preserving user-owned entries. - Detect Kilo from
.kilo/,kilo.json, orkilo.jsoncin applicable generators, onboarding, and project memory. - Generate Kilo rules as Markdown files referenced from
kilo.json[c].instructions, preserving user-owned entries. - Generate Kilo agents under
.kilo/agents/<name>.mdwith documented frontmatter. - Generate Kilo workflows as Markdown files under
.kilo/commands/when the user selects Kilo command generation. - Keep skills in the Agent Skills format. Use
.kilo/skills/for a Kilo-only target; offer.agents/skills/once only when the user explicitly selects a shared location. - State that Kilo hooks require a JavaScript or TypeScript plugin.
- Use
AGENTS.mdas a valid Kilo project-memory wiring surface.
Acceptance criteria
- OpenCode rules are generated through
AGENTS.mdoropencode.json[c].instructions; no generator claims.opencode/rules/as a native rule surface. - A project containing only Kilo signals is detected and proposed by each applicable generator.
- A Kilo rule is referenced from
kilo.json[c]without deleting or reordering existinginstructionsentries. - A Kilo agent is discoverable from
.kilo/agents/and uses current documented frontmatter. - Kilo skills use the Agent Skills payload and shared
.agents/skills/placement only after explicit user selection. - Kilo workflows are generated as Markdown files under
.kilo/commands/when selected. - Each tool-path claim links to an official source and records its verification date.
Relations
- feat(cli): emit rules and commands in OpenCode flat builds #789 owns flat OpenCode distribution.
- feat(cli): emit rules in Kilo flat builds #868 owns flat Kilo rule distribution and is blocked by feat(cli): add Kilo Code support #744.
- feat(cli): add Kilo Code support #744 owns the CLI Kilo profile; this issue does not depend on its draft PR.
Out of scope
- Flat archive emission, including Kilo command distribution; this requires a separate flat-build capability after feat(cli): add Kilo Code support #744.
- Kilo plugin implementation.
- Kilo lifecycle hooks and plugins, owned by feat(cli): add Kilo Code support #744.
Activity
[-]fix(aidd-context): generate native Kilo and current OpenCode artifacts[/-][+]feat(aidd-context): add Kilo support and correct OpenCode rule guidance[/+]blafourcade commentedon Sep 14, 2026
Official OpenCode documentation confirms that project rules are provided through
AGENTS.mdand Markdown files referenced byopencode.json[c].instructions..opencode/rulesis not a documented native rule surface, so the corresponding05-rule-generatereference must be corrected.This issue owns that OpenCode rule correction together with Kilo detection and direct-generation guidance:
kilo.json[c].instructions..kilo/agents/..kilo/skills/for a Kilo-only target, or.agents/skills/once when the user explicitly selects a shared location.AGENTS.md.Kilo does not document
.kilo/commandsas a native Markdown command surface. Reusable workflows are therefore offered as skills, not generated commands. Flat OpenCode distribution remains #789; flat Kilo rules remain #868.blafourcade commentedon Sep 14, 2026
Kilo does document Markdown workflows under
.kilo/commands/(and under~/.config/kilo/commands/for user scope). The current statements that Kilo commands have no native Markdown format are therefore incorrect.Keep this issue focused on
aidd-context: align Kilo detection and generation guidance with the documented surfaces. Archive emission remains outside this issue and belongs to the CLI distribution work after #744.Update the scope rationale accordingly: Kilo command archive emission is excluded for ownership and sequencing, not because Kilo lacks a native command surface.
waewoo commentedon Sep 14, 2026
Thanks for the correction. You’re right that Kilo documents Markdown workflows under
.kilo/commands/.I updated #788 to keep direct Kilo command generation in scope and removed the incorrect claim that Kilo lacks a native Markdown command surface. Flat Kilo command distribution remains out of scope and will be tracked separately after #744.
blafourcade commentedon Sep 23, 2026
Superseded by #913 and #914. #913 owns the observed OpenCode rule-wiring defect; #914 owns Kilo-native generation across aidd-context. The split restores separate artifact types and acceptance contracts without dropping scope. #789 remains OpenCode flat distribution, #868 remains Kilo flat distribution, and #744 delivered the CLI Kilo profile.