feat(framework): ticket format specifies .plan.md (#791)#792
Merged
Conversation
suleimansh
added
enhancement
suleimansh
marked this pull request as ready for review
July 19, 2026 17:45
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
1 participant
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.
Closes #791
#684 was updated after PR #686 shipped, adding
tickets/<DATE>_<SLUG>.plan.mdto the spec. The shippedprompts/ticketing_format.mdonly covered the ticket and the spike, so an agent asked for a plan had no shape to follow.Adds the plan section:
# [Plan] Ticket title,## TLDR,## Plan, optional## Hard problemsand## Variability, plus the typical-content list (exhaustive aspects, the 0-10 "is there an obviously optimal way" rating, alternatives for low ratings).On
<SHOW_CHOICES>: no new UX. The agent already carries theawait-choicesblock from the await protocol, so the line reads "ask the user to pick one with showChoices() and AWAIT (one question per aspect, recommending the alternative you'd pick)". Nothing postponed post-MVP.Prompt text only;
prompts.generated.tsis regenerated at build.Verified:
check:prompt-driftin sync,typecheckclean. The 9 daemon test failures in a fresh worktree are pre-existing and environmental, identical with the change stashed.