-
Notifications
You must be signed in to change notification settings - Fork 0
[Stage 3] Define why, explain, and ci command UX boundaries #91
Copy link
Copy link
Open
Labels
area: cliarea: docshelp wantedExtra attention is neededExtra attention is neededneed helpContribution wanted; scoped but needs implementation or research helpContribution wanted; scoped but needs implementation or research helposs first friendlyFriendly for first open source contributions and automated contributorsFriendly for first open source contributions and automated contributorsstage: 3status: blockedBlocked by another issue or design decisionBlocked by another issue or design decision
Description
Metadata
Metadata
Assignees
Labels
area: cliarea: docshelp wantedExtra attention is neededExtra attention is neededneed helpContribution wanted; scoped but needs implementation or research helpContribution wanted; scoped but needs implementation or research helposs first friendlyFriendly for first open source contributions and automated contributorsFriendly for first open source contributions and automated contributorsstage: 3status: blockedBlocked by another issue or design decisionBlocked by another issue or design decision
Type
Fields
Give feedbackNo fields configured for issues without a type.
Goal: define how existing why/fails behavior should relate to planned explain and ci commands.
Related plan: #82.
Depends on: #27, #28, and #79.
Acceptance criteria:
- Define user intent for why, explain, and ci.
- Clarify default output formats and exit-code expectations.
- Avoid breaking Stage 1/2 command behavior.
- Include examples for local developer and CI usage.