Add SpecKit Companion canvas extension

[alfredoperez]

Pull Request Checklist

• I have read and followed the CONTRIBUTING.md guidelines.
• I have read and followed the Guidance for submissions involving paid services.
• My contribution adds a new instruction, prompt, agent, skill, workflow, or canvas extension file in the correct directory.
• The file follows the required naming convention.
• The content is clearly structured and follows the example format.
• I have tested my instructions, prompt, agent, skill, workflow, or canvas extension with GitHub Copilot.
• I have run npm start and verified that README.md is up to date.
• I am targeting the main branch for this pull request.

---

Description

SpecKit Companion is a board for GitHub Spec Kit projects in the Copilot app. It lists every spec in the repository with the step it is on, opens a spec to read its documents, tasks and run times, and one button sends the next step's command to the session.

It reads the spec files the project already has, so it works with stock Spec Kit and needs no account, service or key. It is free and MIT licensed.

This adds two folders: extensions/speckit-companion/ (the canvas source, with extension.mjs at its root) and plugins/speckit-companion/ (plugin.json and the README). npm run plugin:validate and npm start both ran clean.

Source and tests: https://github.com/alfredoperez/speckit-companion/tree/main/apps/copilot-canvas

---

Type of Contribution

• New instruction file.
• New prompt file.
• New agent file.
• New plugin.
• New skill file.
• New agentic workflow.
• New canvas extension.
• Update to existing instruction, prompt, agent, plugin, skill, workflow, or canvas extension.
• Other (please specify):

---

Additional Notes

The board only reads the project's files and sends one chat message per button press. It writes one small record of the steps it sent, inside the spec's own folder, so it can show how long each took.

---

By submitting this pull request, I confirm that my contribution abides by the Code of Conduct and will be licensed under the MIT License.

[github-actions]

🔒 PR Risk Scan Results

Scanned 20 changed file(s).

Severity	Count
🔴 High	0
🟠 Medium	1
ℹ️ Info	0

Severity	Rule	File	Line	Match
🟠	unpinned-version-indicator	extensions/speckit-companion/package.json	15	"@​​github/copilot-sdk": "latest"

Skipped non-text or missing files

• extensions/speckit-companion/assets/preview.png

This is an automated soft-gate report. Findings indicate review targets and do not block merge by themselves.

[github-actions]

🚦 Submission status: 👀 Ready for review

Risk tier: merge-risk:high — Privileged execution, automation, or review-policy change
Required to merge: passing submission-gate checks plus 2 approvals from reviewers with write access, including a maintainer with admin or maintain permission.

Why this tier

• extensions/speckit-companion/vendor/viewer.css has no diff available to scan for privileged capabilities

Automated checks

Check	Status	Details
Line endings	✅ Passed	Passed · logs
Spelling	✅ Passed	Passed · logs
Generated README consistency	✅ Passed	Passed · logs
Plugin and extension validation	✅ Passed	Passed · logs
Canvas extension validation	✅ Passed	Passed · logs
Plugin structure	✅ Passed	Passed · logs
Risk scan	✅ Passed	Passed · logs
Contributor reputation	✅ Passed	Passed · logs
Duplicate resource scan	✅ Passed	Passed · logs
PR quality signal	⏭️ Skipped	Skipped by its workflow · logs
Canvas/plugin smoke test	⏭️ Skipped	Not reported for this commit

Review

• Approvals: 0/2
• Assigned reviewer: not assigned yet — comment /request-review to ask for one
• Review target date: not set
• Still needed: 2 more approval(s); an approval from a maintainer with admin or maintain permission
• The core-maintainers pool is not staffed yet; an approver with admin or maintain permission is required instead.

Commands

Command	Who	What it does
/rerun-checks	PR author, maintainers	Re-runs failed or incomplete checks and re-evaluates this gate
/request-review	PR author, maintainers	Asks the review rotation to assign a reviewer (adds needs-reviewer)

_{Updated for 939669a · gate run · This comment is maintained automatically — see submission gate docs.}

[aaronpowell]

I think it would be better to contribute this to the Spec Kit repo directly so that it can be bootstrapped as part of a Spec Kit setup in a repo rather than having a need to find it in an external feed.

But if there isn't a desire from the Spec Kit team to have it as part of their repo we can host it