You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Rewrite AGENTS.md to reflect the integration subpackage architecture shipped in #1924. The current content describes the old AGENT_CONFIG dict-based process and references removed artifacts (release ZIPs, case-statement scripts, --ai-skills flags).
Problem
AGENTS.md is consumed by AI coding agents working on the codebase. Stale instructions cause agents to follow the old 7-step process (edit AGENT_CONFIG, update help text, modify release scripts, add case statements, etc.) instead of the current approach.
What to keep
About Spec Kit and Specify — still accurate
Command File Formats (Markdown, TOML) — still accurate, compact reference
Argument Patterns — still accurate, rarely changes
Summary
Rewrite AGENTS.md to reflect the integration subpackage architecture shipped in #1924. The current content describes the old
AGENT_CONFIGdict-based process and references removed artifacts (release ZIPs, case-statement scripts,--ai-skillsflags).Problem
AGENTS.md is consumed by AI coding agents working on the codebase. Stale instructions cause agents to follow the old 7-step process (edit
AGENT_CONFIG, update help text, modify release scripts, add case statements, etc.) instead of the current approach.What to keep
What to remove
config,registrar_config); creates maintenance drift.specify integration list(Addspecify integrationsubcommand for post-init integration management #2065) will provide this programmatically.AGENT_CONFIG, release scripts, case statements,--ai-skillsflag — all removedkey, not dict key)requires_clifield in each integration classregistrar_config.dirin each integrationWhat to write
The new guide should cover:
1. Architecture overview
Brief description of the integration subpackage structure:
integrations/<key>/2. Decision tree: which base class?
MarkdownIntegrationTomlIntegrationspeckit-<name>/SKILL.md)SkillsIntegrationIntegrationBasedirectly3. Configure it (4 required fields)
key— matches actual CLI tool nameconfig— name, folder, commands_subdir, install_url, requires_cliregistrar_config— dir, format, args, extensioncontext_file— path to agent context file (optional)4. Register it
One import + one
_register()call in_register_builtins()5. Add scripts
scripts/update-context.shandscripts/update-context.ps1(~5 lines each)6. Test it
specify init --integration <key>+ install/uninstall round-trip7. Optional overrides
command_filename()for custom output patternsoptions()for integration-specific CLI flagssetup()for custom install logicDepends on