This website requires JavaScript.
Explore
Help
Sign in
singularity
/
singularity-forge
Watch
1
Star
0
Fork
You've already forked singularity-forge
0
Code
Issues
Pull requests
Projects
Releases
Packages
Wiki
Activity
Actions
1
16db710468
singularity-forge
/
TODO.md
6 lines
33 B
Markdown
Raw
Normal View
History
Unescape
Escape
TODO: feature requests for batch backlog ingestion + probe-based resolution Real dogfood for the auto-triage feature: this is the unstructured dump that the autonomous cycle should pick up and process into proper backlog items the next time it runs. Until auto-triage is wired up, the contents serve as a written spec for what's needed. Two flagship features: - Auto-triage TODO.md on each autonomous cycle. `commands-todo.js` already implements `/todo triage` (manual). Wire it to the autonomous orchestrator and skip when TODO.md == _EMPTY_TODO. - When the LLM would ask a clarifying question, replace with parallel combatant + partner probes (adversarial-challenge + collaborative- research) and only fall back to asking a human if probes diverge AND interactive mode is available. This unblocks unattended `headless new-milestone` (the gap that blocked batch backlog ingestion today). Plus five smaller items (headless milestone stall fix, bulk import-roadmap, TTY-free plan list, hand-authorable milestone scaffold, discoverable --answers schema) carried over from the centralcloud-ops SF-IMPROVEMENTS.md observations. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-11 19:09:26 +02:00
# TODO
TODO: triage should escalate Tier 1 items to real milestones Today's triage run confirmed the manual `/todo triage` workflow works, but it stops at tier-listing items in BUILD_PLAN.md — doesn't scaffold .sf/milestones/MNNN/ dirs for the Tier 1 ones. That's the gap that needs closing for the autonomous flow to actually create milestones from raw TODO dumps. Also captures the non-fatal phases-helpers.js extension load error that appeared at the top of the triage run output. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-11 19:15:33 +02:00
Dump anything here.
TODO: feature requests for batch backlog ingestion + probe-based resolution Real dogfood for the auto-triage feature: this is the unstructured dump that the autonomous cycle should pick up and process into proper backlog items the next time it runs. Until auto-triage is wired up, the contents serve as a written spec for what's needed. Two flagship features: - Auto-triage TODO.md on each autonomous cycle. `commands-todo.js` already implements `/todo triage` (manual). Wire it to the autonomous orchestrator and skip when TODO.md == _EMPTY_TODO. - When the LLM would ask a clarifying question, replace with parallel combatant + partner probes (adversarial-challenge + collaborative- research) and only fall back to asking a human if probes diverge AND interactive mode is available. This unblocks unattended `headless new-milestone` (the gap that blocked batch backlog ingestion today). Plus five smaller items (headless milestone stall fix, bulk import-roadmap, TTY-free plan list, hand-authorable milestone scaffold, discoverable --answers schema) carried over from the centralcloud-ops SF-IMPROVEMENTS.md observations. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-11 19:09:26 +02:00
TODO: cross-repo triage + slash-command routing + structured tiers (redo) Previous commit (1fb4b9882) captured only the reset and lost my intended additions due to a Read/Write race. Re-applying the four feature requests from today's dogfooding session: - Cross-repo `triage-all-repos` (real fix for the "many TODO.md files" surface area — single tool, per-repo SF dbs, unified read-only aggregation view). - Slash-command routing fix (`/todo triage` is currently re-implemented by the agent's LLM, bypassing the typed backend; patches to commands-todo.js were silently inert). - Structured tier/priority per triage item (today tiers exist only in LLM-prose appended to BUILD_PLAN.md; no parser-friendly field for "promote Tier 1 items"). - Phases-helpers stale-export error that fires on every SF run; needs either the missing export restored or a test that catches it. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-11 19:34:49 +02:00
---
Reference in a new issue
Copy permalink