Skip to content

work-items/decompose: carry the Brief's goal and constraints into each item #7605

Description

@kyle-sexton

Parent

Refs #7587 (verification and implementation). Source: PLAN Phase 2, topic poteto-review.

Depends on

Outcome

/work-items:decompose run without a spec container carries the Brief's Goal and Constraints into
each item it publishes.

Decisions

  • R5 of the intent chain (D95). Origin: ours.

Key interfaces

None beyond the decompose item template (Parent, Depends on, Outcome, Key interfaces, Done when, Out of
scope).

Done when

  • An eval case added to decompose shows a no-container item body carrying the Brief's Goal and
    Constraints; it fails on main and passes after.
  • bash plugins/skill-quality/scripts/check-skill.sh plugins/work-items/skills exits 0.

Out of scope

  • The container path, which already carries the Brief.
  • Merging unattended: the PR carries do-not-merge until the Merge authority thread passes (B10).

Activity

  1. kyle-sexton commented on Oct 16, 2026

    @kyle-sexton
    MemberAuthor
    No description provided.
  2. added
    needs-triageNot yet classified. Floor until a type and one priority tier are set.
    on Oct 16, 2026
  3. github-actions commented on Oct 16, 2026

    @github-actions
    Contributor

    Understood: this asks /work-items:decompose, when run without a spec container, to carry the Brief's Goal and Constraints into the body of each published item, so no-container items retain that context (the container path already does). Done-when criteria are concrete: an eval case showing a no-container item carrying Goal/Constraints, failing on main and passing after, plus check-skill.sh passing on plugins/work-items/skills. The issue is well-specified, scoped, and lists its dependencies (#7594, #7596, #7599) and parent (#7587) explicitly, with the PR expected to carry do-not-merge until those land. No duplicate found covering this specific no-container carry-through behavior. Nothing appears missing for someone to start the implementation once the listed dependencies are unblocked.

    Automated triage. A maintainer reviews it.

  4. added
    needs-specNeeds a Brief or plan before anyone can build it.
    and removed
    needs-triageNot yet classified. Floor until a type and one priority tier are set.
    on Oct 16, 2026
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.

    Fields

    Work status

    needs-spec

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions