[pull] main from tldraw:main#575
Merged
Merged
Conversation
In order to make `/issue` useful for quick, low-context reports without sending downstream agents past missing intent, this PR creates issues immediately and then matures them through a confidence-scored follow-up flow. The old flow front-loaded codebase research before creating the issue. The new flow inverts that: create the issue from the user's initial description, read back the problem in product terms, score how complete the captured intent is, and ask the questions that would fill the gaps — updating the issue in place as answers arrive. ### What changes - **Create first, mature later.** The skill creates the issue right away so the user can track it, rather than researching the codebase to death first. - **Standard body shape.** The body starts with the user's verbatim description, then a short product-facing **readback** of the problem, a numbered list of **Open questions**, and a plain-text **Confidence** status line (e.g. `Confidence: 84%, ready to get started.`). - **Light investigation.** Codebase searching is kept to just enough to ground the confidence score and ask sharp questions. Anything answerable from the code should not become an open question, and implementation breadcrumbs (file paths, function names, fix recipes) stay out of the body unless the user asks for them. - **Q&A loop.** As the user answers, the issue is updated via `gh issue edit`: answers are written beneath each question, the readback is revised, the confidence line is recomputed, and the issue framing (title, type, labels) can be adjusted if an answer changes what the issue is. - **Critical vs. deferred questions.** Questions prefixed `Critical:` block readiness and cannot be skipped. Non-critical questions the user chooses not to answer are marked `_Deferred by user; not blocking implementation._` and do not block. - **Downstream guardrails.** The `take` skill now treats unresolved `Critical:` questions, `_Awaiting answer._` placeholders, and the `More Info Needed` label as blockers before implementation. - **Issue type helper.** `skills/issue/scripts/set-issue-type.sh` sets GitHub issue types via GraphQL because `gh issue create --type` is unreliable across versions. ### Change type - [x] `other` ### Test plan 1. Read the `/issue` workflow and confirm follow-up answers retrigger the skill and update the issue body in place. 2. Read the `write-issue` standards and confirm the readback, open questions, and deferred-question conventions are documented. 3. Read the `take` workflow and confirm unresolved agent-drafted questions block implementation. 4. Run `git diff --check`. ### Code changes | Section | LOC change | | -------------- | ---------- | | Config/tooling | +110 / -23 |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.4)
Can you help keep this open source service alive? 💖 Please sponsor : )