Skip to content

session-flow: retro findings, catch-up scope and recommend-skills router #7575

Open
2 of 2 issues completed
Open

Description

@kyle-sexton

Parent

Refs #7555. Source: PLAN Phase 7, topic poteto-review. Thread: session-flow.

Depends on

Outcome

The retro carries Matt's findings and is offered, not forced, at chain end; /session-flow:orient
answers "what are we doing?" since the user's last message; one router,
/session-flow:recommend-skills, shortlists skills from an index of every skill.

Decisions

  • Retro absorbs Matt's retro: "no guardrail for this mistake" and "unwired or broken check" findings,
    information-access and no-op-in-steering-file categories, writing-for-agents yardstick, pointer
    after a long search, tool-economy finding (D9, D48, Q524). Origin: Matt's.
  • Retro offered at chain end, not forced; unapplied lessons go to the buffer; value measured by
    lessons absorbed (D50 item 10). Setting: retro offer at chain end offer (user).
  • Retro trends moves to /session-flow:audit-sessions, the all-transcripts source for codify (D50
    item 3, D53).
  • /session-flow:orient gains a since-your-last-message scope (anchor: the user's last own
    message), "Needs you" first, per-item decision, why now, options, recommendation, if unanswered,
    unknowns; live re-check of every PR, run and agent touched; ketchup's current item shape and order
    (D67, Q562; Lauren's ketchup). Setting: catch-up word cap 250 (150 available, user).
  • Orient covers this conversation plus live sessions waiting on the owner; orient all rolls up
    lanes, default one machine, /fleet:reach only in the owner's setup (D87, Q123).
  • One router /session-flow:recommend-skills (renamed from show-options): a script indexes
    frontmatter of all skills (installed, disabled, not installed), the agent shortlists, reads those
    SKILL.md files, may ask one question, never enables or installs (D80, Q157, Q189, Q190; Matt's
    reading of shortlisted skills). Setting: router excludes disabled or uninstalled, default include
    all (user).
  • /session-flow:orchestrate gains a coordinator action (any surface, also as a CLI session) and a
    ## Next naming /planning:draft-goal-condition (Q122, Q526).
  • Workflow continuation: /clear stays resumable; mid-phase, hand bulk work to subagents before
    compacting; handoff and questionnaire files stay in the memory dir (Q525, Q543, Q544).
  • Rejected: forced retro; orient answering chat pings; persona-named routers; a coordinator tied to
    Claude Projects.

Key interfaces

From the design's module layout: "session-flow: retro absorbs Matt's findings; retro trends
moves to /session-flow:audit-sessions. orient gains the since-your-last-message scope.
show-options renamed /session-flow:recommend-skills. orchestrate gains a coordinator action
and a ## Next naming /planning:draft-goal-condition."

Settings: "Catch-up word cap 250 ... Retro offer offer."

Slices, filed when this phase starts: retro-absorb-and-trends-move, orient-catch-up,
recommend-skills, orchestrate-coordinator.

Done when

  • The recommend-skills skill directory exists, show-options does not, and
    rg -n 'session-flow:show-options' plugins docs --glob '!**/CHANGELOG.md' --glob '!.changes/**'
    prints nothing.
  • bash plugins/skill-quality/scripts/check-skill.sh plugins/session-flow/skills exits 0.
  • Every slice sub-issue is closed by a merged PR, each skill-body cut with before/after evals.

Out of scope

  • Chat-ping answers (communication).
  • Description trims, which follow the Skill authoring thread's pilot.

Activity

  1. added
    needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.
    on Oct 16, 2026
  2. github-actions commented on Oct 16, 2026

    @github-actions
    Contributor

    Proposed work class: work-class: structural
    Basis: automated intake triage; the lanes App applied this class.

    Size: Large
    Complexity: Medium
    Uncertainty: Known
    Flags: none
    Blocked by: none

    Understood: this phase issue changes the session-flow plugin in four slices. They are the retro absorbing Matt's findings (with trends moving to audit-sessions), the orient since-your-last-message scope, the show-options to recommend-skills router rename, and the orchestrate coordinator action. The outcome, decisions and done-when checks are specific, so I have no open questions. The work is too big for one change, so it needs splitting into the four slice sub-issues the body names. The dependencies #7571–#7574 did not appear among the newest open issues, so I listed no blockers. Please confirm they are done. No likely duplicates found.

    Automated triage, applied by the lanes App.

  3. changed the issue type fromtoon Oct 16, 2026
  4. changed the issue type fromtoon Oct 16, 2026
  5. removed
    needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.
    on Oct 24, 2026
  6. kyle-sexton commented on Oct 24, 2026

    @kyle-sexton
    MemberAuthor

    Released for re-triage under the owner's 2026-10-24 rule: an issue stops for a person only for an intent or vision question, a security call, a host or attended run, or spend outside prepaid credit. The hold label came off and intake triage runs again now; it re-applies a hold, with a numbered question, when one of those applies.

    To hold this issue again, add needs-human (or status: needs-decision) and say why in a comment.

  7. added
    needs-triageNot yet classified. Floor until a type and one priority tier are set.
    priority: mediumReal value, no hard deadline; normal backlog flow.
    and removed
    needs-triageNot yet classified. Floor until a type and one priority tier are set.
    on Oct 24, 2026
  8. added
    status: readyTriaged, unblocked, and fully specified; eligible to pick up.
    work-class: structuralRefactors, migrations, contract changes; cross-cutting and hard to reverse.
    status: needs-decisionAwaiting a human or maintainer judgment call.
    and removed
    status: readyTriaged, unblocked, and fully specified; eligible to pick up.
    on Oct 24, 2026
  9. melodic-automation-lanes commented on Oct 24, 2026

    @melodic-automation-lanes
    Contributor

    Not admitted to the issue lane yet: Size large: the split into sub-issues at intake is pending (owner Q93).

  10. melodic-automation-lanes commented on Oct 24, 2026

    @melodic-automation-lanes
    Contributor

    The latest triage verdict holds nothing: the issue is at status: ready.

  11. kyle-sexton commented on Oct 26, 2026

    @kyle-sexton
    MemberAuthor

    Released for re-triage under the owner's 2026-10-24 rule: an issue stops for a person only for an intent or vision question, a security call, a host or attended run, or spend outside prepaid credit. The hold label came off and intake triage runs again now; it re-applies a hold, with a numbered question, when one of those applies.

    To hold this issue again, add needs-human (or status: needs-decision) and say why in a comment.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    needs-specNeeds a Brief or plan before anyone can build it.priority: mediumReal value, no hard deadline; normal backlog flow.status: readyTriaged, unblocked, and fully specified; eligible to pick up.work-class: structuralRefactors, migrations, contract changes; cross-cutting and hard to reverse.

    Fields

    Work status

    needs-spec

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions