Skip to content

Tags: github/spec-kit-copilot

Tags

copilot-assess-ask-questions-v1.0.0

Toggle copilot-assess-ask-questions-v1.0.0's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
docs: add canvas dashboard screenshots to READMEs (#10)

Add representative screenshots of the three canvas dashboards (assess,
sdd, bugfix) under docs/images/, embed each in its canvas README, and add
a preview gallery to the main README Canvases section.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 67e10b91-ec1e-4736-af95-f12945cf62b9

copilot-sub-agents-v1.0.0

Toggle copilot-sub-agents-v1.0.0's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Add official Copilot-specific Spec Kit presets (copilot-sub-agents, c…

…opilot-assess-ask-questions) (#9)

* Add official Copilot-specific Spec Kit presets

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

* Align preset release tooling with upstream conventions

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

* Make this repo the sole home for the Copilot presets

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

* Rename assess-ask-questions preset to copilot-assess-ask-questions

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

* Revert catalog advertising in speckit-preset skill

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.

* Fix preset catalog install docs: require --name and --install-allowed

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.

* Document GitHub release install (--from) in preset READMEs

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.

* Frame catalog+id install as recommended; --from and --dev as escape hatches

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.

* Point preset URLs at canonical github/spec-kit-copilot repo

Update catalog_url, download_url, repository, homepage, documentation, and
README install commands from the mnriem fork to the canonical github org repo.

* Address PR #9 review feedback on Copilot presets

- Raise copilot-sub-agents floor to Spec Kit >=0.8.0 (composition strategies
  prepend/append/wrap landed in v0.8.0); align preset.yml, catalog.json, and all
  three README tables.
- Narrow the 'all core commands' claim to the eight workflow commands actually
  shipped (constitution/converge are not covered) in preset.yml, catalog.json,
  and the preset README.
- Make the copilot-sub-agents README install section self-contained (register
  catalog + install by id, with --from/--dev as escape hatches).
- Fix speckit.plan delegation: run data-model + contracts in parallel, then
  generate quickstart (which depends on their output).
- Fix speckit.taskstoissues delegation: preserve the core dedup pass and only
  parallelize unmatched task IDs to avoid duplicate issues on reruns.
- Correct the assess --dev path to ./spec-kit-presets/copilot-assess-ask-questions.
- Repair the broken 'Parallelism by Command' markdown table (stray blank line).
- Harden release-preset.yml to fail when the tag version doesn't match preset.yml
  and the catalog entry.