Add official Copilot-specific Spec Kit presets (copilot-sub-agents, copilot-assess-ask-questions) - #9
Open
mnriem wants to merge 10 commits into
Open
Add official Copilot-specific Spec Kit presets (copilot-sub-agents, copilot-assess-ask-questions)#9mnriem wants to merge 10 commits into
mnriem wants to merge 10 commits into
Conversation
Promote copilot-sub-agents and assess-ask-questions from the experimental mnriem/spec-kit-presets repo into an isolated spec-kit-presets/ subtree with its own catalog.json, so Spec Kit (specify preset) plumbing is not confused with Copilot (copilot plugin) plumbing. - spec-kit-presets/: two presets + scoped catalog.json + boundary README - scripts/build-presets.sh: deterministic zip packaging (preset.yml at root) - .github/workflows/release-preset.yml: publish <preset>.zip on <preset>-v* tag - AGENTS.md/README/speckit-preset: document the boundary and catalog URL - gitignore preset build artifacts
Replace the standalone build-presets.sh + custom workflow with the upstream mnriem/spec-kit-presets release pattern, path-adjusted for spec-kit-presets/: - release-preset.yml: on <preset>-vX.Y.Z tag, zip the preset inline (no build script) and gh release create the asset; notes from optional CHANGELOG.md - release-preset-trigger.yml: workflow_dispatch (preset id + version) that validates and pushes the tag - Drop scripts/build-presets.sh and the dist/ gitignore - Update AGENTS.md + spec-kit-presets/README versioning to the CI mechanism
Remove all references to the origin mnriem/spec-kit-presets repo now that these Copilot-specific presets live canonically here: - Drop 'promoted from experimental upstream' framing in AGENTS.md/READMEs - Repoint preset.yml repository fields to mnriem/spec-kit-copilot - Fix assess-ask-questions install docs to the local catalog URL - Drop 'mirrors upstream' notes from the release workflows
Adopt a consistent copilot-<scope> naming convention for Copilot-specific presets (distinct from the spec-kit-copilot-* plugin namespace): - Rename dir + preset.yml id to copilot-assess-ask-questions - Display name -> 'Copilot Assess Clarifying Questions' - Update catalog key/id/download_url/documentation and tag/asset scheme - Update README/AGENTS/SKILL references and in-preset command labels - Document the naming convention in AGENTS.md
Keep the generic speckit-preset command-wrapper skill decoupled from this repo's specific preset content. The catalog URL and install commands remain documented in spec-kit-presets/README.md and the top-level README.
Preset catalogs are added discovery-only (read-only) by default and --name is required (confirmed against github/spec-kit presets source). The catalog.json carries no install policy; install_allowed lives in the consumer's .specify/preset-catalogs.yml. Update both README install snippets to add the catalog installable, and document the discovery-only default in the speckit-preset skill's generic catalog syntax + notes.
Restore the install-from-GitHub-release-zip method (dropped when removing upstream refs). Both READMEs now show catalog, --from <release url>, and --dev (local development) paths. The --from URLs match catalog.json download_url.
…atches Present 'register catalog once, then add by id' as the primary path in both preset READMEs, with --from (one-off, no catalog) and --dev (local dev) clearly marked as fallbacks.
Update catalog_url, download_url, repository, homepage, documentation, and README install commands from the mnriem fork to the canonical github org repo.
…presets # Conflicts: # README.md
mnriem
requested
a balanced review from Copilot
and removed request for
Copilot
August 6, 2026 17:09
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds two Copilot-specific Spec Kit presets as their official, sole home, under an isolated
spec-kit-presets/subtree with its owncatalog.json:copilot-sub-agents>= 0.2.0runSubagent, Copilot CLI sub-agents,.github/agents/copilot-assess-ask-questions>= 0.9.0+ built-inassessextensionask_usertool (no plain-text fallback)Plumbing boundary
These are not Copilot plugins — they're consumed by the
specifyCLI (specify preset add). They live in their own subtree with a dedicatedcatalog.jsonso Spec Kit plumbing is never confused with the Copilot plugin/marketplace plumbing. Naming convention (copilot-<scope>, display name leads with "Copilot") is documented inAGENTS.md.Release automation
.github/workflows/release-preset.yml+release-preset-trigger.ymlfollow the upstream spec-kit two-workflow pattern (inline zip, no build script) so preset zips publish as release assets matching the catalogdownload_urls.Verification
specify preset add --dev);preset.ymlandcatalog.jsonvalidate against the upstream schema.speckit-planskill = our delegation content + the full core plan body.{CORE_TEMPLATE}placeholder; strategy values valid.main.Follow-up after merge
Cut releases by pushing tags
copilot-sub-agents-v1.0.0andcopilot-assess-ask-questions-v1.0.0(or run Release Preset Trigger) so the catalogdownload_urls resolve. The rawcatalog_urlresolves once this lands onmain.