chore(tasks): queue tech-lead-curated hardening + simplification (10h grind)#49
Merged
Merged
Conversation
Stage 7 actionable tasks for the 2026-05-03 10h taskgrind run with focus on user-stories hardening and feature simplification. - P1: spec-metadata coverage gap (Blocked, Research, Parent, Last-enriched, standing loops, policies are first-class fields per spec.md but never appear in user stories) - P1: tasks watch --fix doc/code mismatch (story 01 line 132 false promise; cli.ts:113-120 has no --fix flag) - P2: consolidate sync-issues|jira|linear into tasks sync <provider> - P2: add tasks list to close CLI/MCP API drift with list_tasks - P2: sharpen vague acceptance in stories 03/04/05 (batched >=3) - P2: README CLI table + watch/diff visibility + sync defaults (batched >=3 docs findings) - P2: story 02 backtick + story 07 pick docs + story 03 pick-vs-next-task (batched >=3 polish findings) Each task is sized for one PR. Doc batches respect Rule 9 (no single-finding doc-drift PRs). Existing blocked tasks preserved. --- _🤖 Written by an agent, not Fyodor. Ping me if this looks off._
2 tasks
fyodoriv
added a commit
that referenced
this pull request
May 3, 2026
Mid-grind refill at 12:13 EDT. The tech-lead-curated queue from PR #49 was burned through in ~50min (PRs #51-#57). Restocking with 5 substantive tasks aligned with the same focus axes. P1: - cli-restore-json-on-read-commands — undo a partial regression that removed --json from pick/stats/diff but kept it on the new list cmd - user-stories-runnable-demos — add Try-it-yourself sections to all 8 stories so claims become reader-verifiable P2: - cli-pick-show-details — print full Details block in pick output - readme-worked-example — first-10-min walkthrough connecting stories - cli-watch-monorepo-coverage — discoverWatchFiles integration test for monorepo shape (story 05's promise is unverified today) - user-stories-install-detect-docs — story 03 doesn't say which dirs trigger which agent install Each task is sized for one PR. Doc batches respect Rule 9 (>=3 findings batched). --- _🤖 Written by an agent, not Fyodor. Ping me if this looks off._
fyodoriv
added a commit
that referenced
this pull request
May 3, 2026
Mid-grind refill at 12:13 EDT. The tech-lead-curated queue from PR #49 was burned through in ~50min (PRs #51-#57). Restocking with 5 substantive tasks aligned with the same focus axes. P1: - cli-restore-json-on-read-commands — undo a partial regression that removed --json from pick/stats/diff but kept it on the new list cmd - user-stories-runnable-demos — add Try-it-yourself sections to all 8 stories so claims become reader-verifiable P2: - cli-pick-show-details — print full Details block in pick output - readme-worked-example — first-10-min walkthrough connecting stories - cli-watch-monorepo-coverage — discoverWatchFiles integration test for monorepo shape (story 05's promise is unverified today) - user-stories-install-detect-docs — story 03 doesn't say which dirs trigger which agent install Each task is sized for one PR. Doc batches respect Rule 9 (>=3 findings batched). --- _🤖 Written by an agent, not Fyodor. Ping me if this looks off._
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.
Why this is needed
Pre-stage queue was 100% blocked (3/3 tasks carried
**Blocked**lines), so the autonomous agent'staskgrind/scripts/check-zero-ship-streak.mjsreturnedSTOPand the 10h grind would hard-exit on Rule 10 without shipping any work. The user wants a productive 10h tech-lead-led grind focused on hardening user stories and simplifying CLI features. This PR files the actionable, unblocked queue that closes that gap.Summary
Stages 7 actionable tasks for the 2026-05-03 10h taskgrind run with explicit tech-lead focus on hardening user stories and simplifying CLI features.
What's queued
user-stories-spec-metadata-coverage**Blocked**,**Research**,**Parent**,**Last-enriched**, standing loops, policies (all first-class spec features absent from user stories)cli-watch-fix-flag-mismatchtasks watch --fixbut no such flag exists incli.ts:113-120cli-simplify-sync-providerssync-issues/sync-jira/sync-linearintotasks sync <provider>(11→9 commands)cli-add-list-commandlist_tasks, CLI does notuser-stories-acceptance-sharpeningdocs-accuracy-batch-readme-cliwatch/diffvisibility, P2-default and Linear-label-normalization in story 06user-stories-polish-batchtasks pickdocs, story 03 pick-vs-next-taskEach task is sized for one PR; doc-only tasks batch ≥3 findings per Rule 9.
Tech-lead pruning
Pruned 5 audit findings that didn't justify their cost:
tasks lintremoval (convenience wrapper, not real surface),init --installremoval (UX win),generate-commandshiding (used by CI),--agentremoval (explicit installs are useful), and small per-finding doc PRs that would fail Rule 9.Test plan
npx -y @tasks-md/lint TASKS.mdpasses (run on the new file before commit)taskgrind/scripts/check-zero-ship-streak.mjsreturnsCONTINUE(wasSTOPbefore)🤖 Written by an agent, not Fyodor. Ping me if this looks off.