feat(framework): "Suggest new tickets" preset (#462)#674
Merged
Conversation
Member
Author
Member
|
I think: too much babysitting => counter productive, less efficient, and brittle. After we have: How about we make this preset to be just this:
That's it. I think this is enough (but let's test it). |
suleimansh
added a commit
that referenced
this pull request
Jul 18, 2026
The Agentic PM ideation preset, shipped like the others as a prompt-kind run. Per #674 the prompt is a single line, "Suggest new tickets": the run-start context fragment (#683) already points the agent at the existing tickets/**.md and the .the-framework/ticketing-format.md spec (#684), so it does not re-teach the ticket format or spell out the flow. An over-specified prompt is babysitting, which is brittle and counter-productive. Paramless: the dashboard prefills the line into the editor and the user edits it freely. Closes #462
suleimansh
force-pushed
the
feat/462-suggest-features-preset
branch
from
July 18, 2026 10:56
8e9a5d1 to
2779fdd
Compare
This was referenced Jul 18, 2026
suleimansh
changed the title
The Agentic PM ideation preset, shipped like the others as a prompt-kind run. Per #674 the prompt is a single line, "Suggest new tickets": the run-start context fragment (#683) already points the agent at the existing tickets/**.md and the .the-framework/ticketing-format.md spec (#684), so it does not re-teach the ticket format or spell out the flow. An over-specified prompt is babysitting, which is brittle and counter-productive. Paramless: the dashboard prefills the line into the editor and the user edits it freely. Closes #462
suleimansh
force-pushed
the
feat/462-suggest-features-preset
branch
from
July 18, 2026 11:59
2779fdd to
9d5ff22
Compare
suleimansh
added a commit
that referenced
this pull request
Jul 18, 2026
The first dogfood output of the Agentic PM ideation preset (#462), kept as backlog per the #624 model where a proposal is just a PR: merge accepts it, close rejects it. Four net-new user-facing feature tickets, each grounded in existing code + open issues, none re-proposing tracked work, named per the #684 ticketing format (tickets/<DATE>_<SLUG>.md, with a TLDR + Why it matters), plus their tickets/TODO.md entries under a 'Proposed (agentic PM, pending confirmation)' section: - PR review bot for human-authored PRs - Multi-agent race / tournament runs - Two-way Discord replies to answer awaiting-gates - Pre-run cost & duration estimate No changeset (repo backlog data, not a package). Refs #462 (the closer is the preset PR #674)
Member
Author
|
Done, reshaped to your line. Chain is #686 (#684 ticket-format spec) -> #687 (#683 context fragment) -> this, both merged. This one is just the single prompt now:
Paramless, the dashboard prefills it and you edit freely. Renamed features -> tickets. Three small calls, want your check before we test:
Ready to dogfood once you ok the wording. |
Member
Author
Member
Only one. Actually TODO_AGENTS.md is a bit more standard than
Correct me if I miss something, but I think better inside |
This was referenced Jul 18, 2026
suleimansh
added a commit
that referenced
this pull request
Jul 18, 2026
Per Rom's #674 call, use the underscore spelling TODO_AGENTS.md (more standard, 'convention over proprietary') instead of the hyphenated TODO-AGENTS.md that #682 shipped. New backlogs are created at TODO_AGENTS.md; the brief hyphen spelling is kept as a read fallback (LEGACY_HYPHEN_TODO_FILE) so no repo loses a backlog, alongside the tickets/TODO.md and root TODO.md fallbacks. Migrates this repo's own backlog file, and expands the GOAL.md context gloss to match the revised #683. Refs #674, #683
suleimansh
added a commit
that referenced
this pull request
Jul 18, 2026
…rialized (#684) Per Rom's #674 call, the ticketing_format.md spec ships inside the package (added to the files allowlist) and the run-start context fragment references it by its node_modules path, so the format versions with the package instead of being materialized into each repo. Removes materializeTicketingFormat + its install call and export. Also adds the revised #684 optional priority: and topics: fields to the ticket body, and lowercases the [optional: ...] hint. Refs #684, #674
suleimansh
added a commit
that referenced
this pull request
Jul 18, 2026
…rialized (#684) (#693) Per Rom's #674 call, the ticketing_format.md spec ships inside the package (added to the files allowlist) and the run-start context fragment references it by its node_modules path, so the format versions with the package instead of being materialized into each repo. Removes materializeTicketingFormat + its install call and export. Also adds the revised #684 optional priority: and topics: fields to the ticket body, and lowercases the [optional: ...] hint. Refs #684, #674
suleimansh
marked this pull request as ready for review
July 19, 2026 00:32
…ures-preset # Conflicts: # packages/framework-dashboard/components/StartRunForm.tsx
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
2 participants
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 #462. The last MVP-v2 item (Agentic PM). Reshaped per your #674 call. Chain: #686 (#684) -> #687 (#683) -> this.
What changed
Dropped the elaborate prompt (the babysitting) for a single line:
The ambient context carries the rest now: the run-start context fragment (#687/#683) points the agent at the existing
tickets/**.mdand the.the-framework/ticketing-format.mdspec (#686/#684), so the prompt does not re-teach the format or spell out the flow.suggest-new-tickets, dashboard label "Suggest new tickets").definePresetdefaultWhattweak the first draft added (no preset needs it now).Depends on
Only makes sense once #686 + #687 land (they provide the context). Independent at the code level; merge those two first.
Tests
suggest-new-tickets-preset.test.tspins the one-liner + paramless shape. Framework + dashboard typecheck clean, preset suite green.