Skip to content

Each task group should have its own testing and documentation updated within the group rather than waiting to add testing and documentation #1952

Description

@keithboone

On more complicated CRs which have multiple task groups, I've noted that Claude and Github Copilot will often add a Task group at the end that involves testing and documentation. This creates a failure mode where a change having 6+ task groups can fail testing at the end because something wasn't tested properly in Task Group 1 or 2, and problems cascade downward through other tasks, involving a lot of rework. My agents have a standing rule to include testing and documentation updates in each task group for the changes made during that group to ensure this doesn't happen, but this instruction really belongs in the Openspec tasks guidance given to agents.

Activity

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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions