Feedback: Please implement the 'agents' tool target (.agents/skills + .agents/commands). It is registered in the tool list as available:false with no skillsDir, so AGENTS.md-based setups have to generate for another tool and move files by hand.

[arabold]

---

Submitted via OpenSpec CLI

• Version: 1.7.0
• Platform: darwin
• Timestamp: 2026-07-29T14:06:57.346Z

[clay-good]

Implemented in #1303 — openspec init --tools agents (and the interactive picker) now installs the workflow skills to .agents/skills/openspec-*/SKILL.md. You were right about the cause: the entry was registered with available: false and no skillsDir, and since every gate in the codebase keys off skillsDir rather than available, it was unreachable everywhere.

One half of your request is deliberately not implemented: .agents/commands is not generated. There is no cross-vendor slash-command format — frontmatter fields, folder namespacing (opsx/<id> vs opsx-<id>), and the invocation prefix (/, @, $, /skill:) all differ per tool, which is why OpenSpec has a separate command adapter per tool rather than one generic one. A generic .agents/commands would write files that no tool reliably reads.

So the target is skills-only, the same as Kimi Code, Hermes, ForgeCode, CodeArts and Mistral Vibe. openspec init says so at install time (Commands skipped for: agents (no adapter)), and the workflows are invoked by skill name — /openspec-propose, /openspec-apply-change.

If a specific assistant you use does read a documented .agents/commands format, please open a follow-up issue naming the tool and linking its docs — that would be an adapter for that tool, which is a shape OpenSpec already supports.