Skip to content

docs(workflow): kg-ideate ideation outputs for 6 backlog leads#514

Open
NikashPrakash wants to merge 1 commit into
masterfrom
chore/ideate-backlog-leads
Open

docs(workflow): kg-ideate ideation outputs for 6 backlog leads#514
NikashPrakash wants to merge 1 commit into
masterfrom
chore/ideate-backlog-leads

Conversation

@NikashPrakash

Copy link
Copy Markdown

Ran the kg-ideate pipeline (KG-grounded brief → spec/plan scaffold) via parallel planning subagents over the fair-game plan/spec backlog leads (workstore-backend excluded — owned by another session; pure code-fixes and payout/omp-scoped items excluded). Each output is grounded in current code + existing specs/plans + lessons, and — per single-source-of-truth — routes into an existing owner where one exists rather than spawning a competing plan.

Docs only (planning artifacts under .agents/workflow/specs/); no code.

Lead Outcome Notes
workflow-store-concurrency NEW spec + plan-draft No active plan owns it (git-ref-work-backend archived, calls the lone withTasksLock an "interim band-aid"); exactly 1 of N RMW writers locked, saves non-atomic. 5 tasks p0–p4.
fold-back-resolution-lifecycle MERGE → agent-ops-hardening da workflow fold-back resolve/reject verb + status model (the manual sweep this session is the missing-verb symptom). 4 tasks.
config-drift-audit MERGE → agent-ops-hardening config-v2-migration already shipped the schema-drift auditor; residual = scaffold↔home + registry-vs-disk drift. 3 tasks.
orientation-landed-work-probe MERGE → full-loop-orchestration-runtime eligible/orient lacks a landed-work (write-scope-vs-master) signal; coordinate shared eligible_accounting.go with layered-pr-fanout. 2 tasks.
loud-atomic-error-handling MERGE → full-loop-orchestration-runtime concern delivered by archived swallowed-errors-loud-atomic (16/16); the never-sliced internal/journal snapshot/recovery swallow family remains. 1 task (se11).
spec-template-non-goals RECLASSIFY → spec-scaffold skill convention Non-Goals block + reworded Deferred; drafted text inline.

Each dir holds design.md+plan-draft.md (the NEW one) or RECOMMENDATION.md (merge/reclassify) with drafted tasks (write-scope + acceptance) so a plan owner can land them directly.

Not done here (owner greenlight): injecting the merge tasks into the active plans, formally creating the new plan (da workflow plan create workflow-store-concurrency), and applying the spec-scaffold convention edit — those mutate active/owned plans and a shipped skill, so they're left for the owners.

Ran the kg-ideate pipeline (KG-grounded brief -> spec/plan scaffold) via
parallel planning subagents over the fair-game plan/spec backlog leads. Each
output is grounded in current code + existing specs/plans + lessons, and — per
single-source-of-truth — routes into an existing owner where one exists rather
than spawning a competing plan.

Outcomes:
- workflow-store-concurrency        NEW spec + plan-draft. No active plan owns
  it (git-ref-work-backend archived, calls the lone withTasksLock an "interim
  band-aid"); exactly one of N RMW writers is locked and saves are non-atomic.
- fold-back-resolution-lifecycle    MERGE -> agent-ops-hardening (4 tasks): a
  `da workflow fold-back resolve/reject` verb + status model (the manual sweep
  in this session is the missing-verb symptom).
- config-drift-audit                MERGE -> agent-ops-hardening (3 tasks):
  config-v2-migration already shipped the schema-drift auditor; residual is
  scaffold<->home + registry-vs-disk drift.
- orientation-landed-work-probe     MERGE -> full-loop-orchestration-runtime
  (2 tasks): eligible/orient lacks a landed-work (write-scope-vs-master) signal.
- loud-atomic-error-handling        MERGE -> full-loop-orchestration-runtime
  (1 task se11): concern delivered by archived swallowed-errors-loud-atomic;
  the never-sliced internal/journal snapshot/recovery swallow family remains.
- spec-template-non-goals           RECLASSIFY -> spec-scaffold skill convention
  (Non-Goals block + reworded Deferred); drafted text inline.

Each dir holds design.md+plan-draft.md (the NEW one) or RECOMMENDATION.md
(merge/reclassify) with drafted tasks (write-scope + acceptance). Landing the
merges into active plans and the skill edit is left for the plan owners.
@sonarqubecloud

Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant