Skip to content

Tighten Method issue templates around sponsor evidence #65

Closed
#66
Closed
Tighten Method issue templates around sponsor evidence#65
#66
Labels
lane:asapHighest-priority Method lane; pull next.legend:processMethod process, workflow, adapters, and CLI work.priority:mediumMedium priority.type:maintenanceMaintenance, cleanup, or operational workflow work.work-in-progressSomeone is actively working this issue.

Description

@flyingrobots
flyingrobots
opened on Jun 1, 2026

Summary

Tighten the GitHub Issue templates added by the tracker migration so bug, spike, and work-item intake all capture Method sponsor seats, witness plans, and artifact links consistently.

Method evidence

  • Sponsored Human: Maintainer or contributor trying to file actionable work.
  • Sponsored Agent: Automation or review agent reading issue bodies for evidence and closeout expectations.

Acceptance criteria

  • Bug, spike, and work-item templates use abstract sponsored human/agent seats.
  • Witness plans name tests, playback, docs, and retro/closeout evidence.
  • Method artifact links are explicit in every relevant template.
  • Sponsor abstractness invariant covers issue cards as well as design docs.

Activity

  1. flyingrobots
    added
    lane:asapHighest-priority Method lane; pull next.
    work-in-progressSomeone is actively working this issue.
    legend:processMethod process, workflow, adapters, and CLI work.
    priority:mediumMedium priority.
    type:maintenanceMaintenance, cleanup, or operational workflow work.
    on Jun 1, 2026

  2. coderabbitai commented on Jun 1, 2026

    @coderabbitai
    coderabbitaibot
    on Jun 1, 2026 – with coderabbitai
    🔗 Related PRs

    #64 - Make GitHub Issues the Method work tracker [closed]

    📝 Issue Planner

    Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.

    • Create Plan
    🧪 Issue enrichment is currently in open beta.

    You can configure auto-planning by selecting labels in the issue_enrichment configuration.

    To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

    issue_enrichment:
  auto_enrich:
    enabled: false

    💬 Have feedback or questions? Drop into our discord!

  3. flyingrobots
    closed this as completedin #66on Jun 1, 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

    lane:asapHighest-priority Method lane; pull next.legend:processMethod process, workflow, adapters, and CLI work.priority:mediumMedium priority.type:maintenanceMaintenance, cleanup, or operational workflow work.work-in-progressSomeone is actively working this issue.

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions