Activity

1. pylot-app

   added

   prd-readyIssue has been structured as a PRDIssue has been structured as a PRD

   ready-to-workPRD complete, cleared for implementation dispatchPRD complete, cleared for implementation dispatch

   on Sep 7, 2026
2. pylot-app commented on Oct 5, 2026

   

   pylot-appbot

   on Oct 5, 2026 – with Pylot App

   Author

   More actions

   Weekly sync update (2026-10-05)

   Fork HEAD is unchanged since this issue was filed: de8114818566742bef02773940457e23db7b6f36. None of the six recommendations below have been cherry-picked yet — all still open and applicable as written.

   Consumer delivery status (re-verified)

   • booster-pack: still nine-of-nine exact match against presets/lean/commands/ + templates/commands/{checklist,clarify}.md. No-op, no PR.
   • inbox-angel-worker: PR Docs setup github/spec-kit#100 (sync/spec-kit-commands-20260817) is still open and still the single live sync PR; confirmed it covers the current drift (including speckit.checklist.md). No duplicate opened.
   • mtg-lotr: now zero drift — PR [suggestion] Support for models using api keys github/spec-kit#45 appears to have merged since this issue was filed. Confirmed clean against templates/commands/.
   • rails-backend: no longer blocked. Git credential mint and repo access both succeeded this run (Lexgo-cl/rails-backend, read via its own org-scoped token). Three of nine files differ from templates/commands/:
     • speckit.checklist.md — genuine drift, byte-identical to the stale content found in inbox-angel-worker before its sync. Opened Lexgo-cl/rails-backend#2137 for this file only. Not merged.
     • speckit.constitution.md, speckit.implement.md — not drift. Commit history on these files (ad348a9, 7c6c55d, c149c30, 666ba8e) shows deliberate rails-backend-specific process content: a mandatory docs/product-principles.md read, references to a product-shaping skill, and bespoke execution-contract language. Left untouched.
   • CLAPES-UC: still blocked, but the cause is now specific — the Pylot GitHub App is not installed on the CLAPES-UC org (gh-shim: no installation token for CLAPES-UC/... — gateway unreachable or App not installed on its org), not a transient 502 as seen previously. This needs a human to install the App on that org (or supply the specific repo name(s) through a path that doesn't depend on it) before any sync or audit of CLAPES-UC repos is possible.

   New upstream commits worth evaluating (merge-base advanced)

   Upstream github/spec-kit has moved from 4a7341a93d944d6efe153b71da4a1adb9c2b578c to 2dda0478 (199 commits). Of those, the ones touching paths the fork actually ships (templates/commands/, scripts/) are:

   1. Medium — needs a terseness-aware semantic port, not a direct patch: b6005769 stops all ten upstream command templates from silently disabling mandatory (optional: false) hooks when .specify/extensions.yml fails to parse — it now reports the parse error and names the skipped mandatory hooks. The fork's terse templates collapsed this whole section to one line (Run hooks.before_clarify from .specify/extensions.yml if present), so there's no silent-skip prose left to patch — but the fork's one-liner has the same underlying gap (a malformed manifest is indistinguishable from "no hooks"). Needs a terse-native rewrite, not a transplant.
   2. Low — needs the same terseness treatment: 98eb2fb4 narrows speckit.clarify's planning-deferral catch-all to implementation-method/tech-stack/task-breakdown only, so spec-taxonomy items (NFRs, acceptance criteria, edge cases) stop getting silently deferred. The fork's clarify.md already collapsed this into a one-line coverage table with no catch-all phrase to bound — check whether the terse version still has the broader bug before deciding this is worth a line.
   3. Low — straightforward, applicable as a one-line addition: 072ab333 has speckit.tasks quote data-model.md field constraints (max length, nullable, enum, validation rules) verbatim into generated task text instead of leaving them to implementation-time discretion. The fork's tasks.md still has the equivalent Entities from data-model.md → map to stories line this would attach to.
   4. Not yet applicable: 68b94af0 (converge.md fix) touches a command the fork still doesn't ship — tracked by item 1 in the existing recommendation list above (converge is missing entirely). Revisit once/if converge lands.
   5. Did not evaluate 0a1b5575 (SPECIFY_FEATURE_NO_PERSIST env var) and 88fd17a8 (SPECKIT_PYTHON override) in depth — both are scripts/bash changes; flagging for a future pass since this run's budget went to the consumer-repo side.

   Adoption boundary (unchanged)

   These remain recommendations only — no upstream commit was cherry-picked, no template rewritten, and no consumer re-baselined in this run. Each accepted item still needs its own reviewed PR against fellowship-dev/spec-kit.

   ---

   Note: #10 and #11 cover overlapping ground from earlier runs of this same weekly sync and look like candidates for consolidation into this issue — not closed here since that wasn't this run's mandate, just flagging for whoever triages next.
3. maxfindel commented on Oct 12, 2026

   

   maxfindel

   on Oct 12, 2026

   More actions

   Weekly sync update (2026-10-12): source fork remains de8114818566742bef02773940457e23db7b6f36. No consumer PR was created. Booster Pack's nine legacy commands match the six lean plus three standard baseline exactly, and it also ships spec-kit skills. Rails has seven standard-template matches and two intentional repo customizations; checklist PR Lexgo-cl/rails-backend#2137 is merged. Existing open PR fellowship-dev/inbox-angel-worker#100 and PR fellowship-dev/mtg-lotr#45 each produce nine-of-nine canonical command blobs at their current heads. The October 5 statement that MTG PR 45 appeared merged is superseded by this live open-state read.

   New upstream recommendation: github/spec-kit v1.1.3, released October 9, includes github/spec-kit#4879, merged October 8 as fa4b81dad128e7130f85e67bb4af52f8a96e0f45: core taskstoissues is deprecated in favor of the bundled GitHub extension, with the existing workflow retained during transition. Our fork still ships core templates/commands/taskstoissues.md, consumed by all four repos. Recommendation: retain the fork command for now; evaluate an explicit fork-compatible GitHub-extension transition before adopting upstream's deprecation warning or removing core. Directly porting the warning would tell users to install an extension the current fork has not verified. Scope a separate reviewed proposal around the current command's deduplication/safety/hooks and actual supported installation model; no automatic extension install, command removal, issue creation or consumer rewrite. This is a compatibility decision, not a bulk upstream upgrade. Prior recommendations remain proposals and have not been applied by this run.