docs(openspec): propose messenger command surfaces#51
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR introduces an OpenSpec change proposal that defines first-class “native” messenger command surfaces (Telegram command menu, Discord /relay application command, Slack /pirelay slash command) derived from PiRelay’s canonical remote command registry, along with setup-wizard requirements and implementation task planning.
Changes:
- Adds a new OpenSpec change (
add-messenger-command-surfaces) with proposal + design describing registry-driven command surface metadata and safety/authorization invariants. - Adds new requirements for Telegram menu registration, Discord namespaced native commands, Slack
/pirelayslash command routing + manifest/setup guidance, and parity/safety testing expectations. - Adds implementation task breakdown and validation checklist for the planned work.
Reviewed changes
Copilot reviewed 6 out of 6 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
| openspec/changes/add-messenger-command-surfaces/tasks.md | Implementation task plan for command-surface helpers, per-platform wiring, tests, docs, and validation. |
| openspec/changes/add-messenger-command-surfaces/specs/relay-setup-tui/spec.md | Modified setup-wizard requirements, including Slack manifest/tab expectations and troubleshooting guidance. |
| openspec/changes/add-messenger-command-surfaces/specs/messenger-command-surfaces/spec.md | New requirements defining Telegram/Discord/Slack native command surfaces, safety invariants, and parity tests/diagnostics. |
| openspec/changes/add-messenger-command-surfaces/proposal.md | High-level motivation, change summary, impacted capabilities, and scope/impact notes. |
| openspec/changes/add-messenger-command-surfaces/design.md | Detailed design goals, decisions, risks/trade-offs, and migration plan for command surfaces. |
| openspec/changes/add-messenger-command-surfaces/.openspec.yaml | Registers the change as a spec-driven OpenSpec change with creation date. |
zikolach
force-pushed
the
openspec/add-messenger-command-surfaces
branch
from
de2b726 to
adc84f7
Compare
zikolach
force-pushed
the
openspec/add-messenger-command-surfaces
branch
from
adc84f7 to
380e8fb
Compare
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.
Summary
/relay, and Slack/pirelaybehaviorValidation
openspec validate add-messenger-command-surfaces --strict