Skip to content

[Task] Validate migrated prompt library and define rollout controls #740

@ashleyshaw

Description

@ashleyshaw

Parent issue: #736

Template source: .github/ISSUE_TEMPLATE/12-testing-coverage.md
Template label: 🧪 Test Coverage
Spec source: .github/projects/active/refactor-migrate-prompts/openspec-strict/children/01-4-task-validation-and-rollout-controls.md


Template Base

Summary

Action

  • Action Type: ☐ Create ☐ Refactor (select one)
  • Target File: <exact path to file to create or refactor>

Proposed Test Content

Scope & Applicability

Acceptance Criteria

  • Test covers all required scenarios and edge cases
  • Test is properly structured and follows conventions
  • Change is documented in the project change log
  • Test has been run and passes as expected
  • Changelog entry prepared for PR if user-facing
  • PR uses correct branch prefix (test/)
  • Approved by at least one maintainer

Definition of Ready (DoR)

  • Purpose, scope, and audience defined
  • Target file and action type specified
  • Acceptance criteria listed
  • Estimate added (if applicable)

Definition of Done (DoD)

  • All acceptance criteria met and verified
  • Changelog entry prepared for PR
  • Test passes all required scenarios and environments
  • Documentation updated (if needed)
  • PR uses correct branch prefix (test/)
  • Approved by at least one maintainer


Spec Details

template-map

  • template_file: .github/ISSUE_TEMPLATE/12-testing-coverage.md

Deliverables

  1. Validation checklist and evidence (format, links, smoke usage).
  2. Known caveats and compatibility notes.
  3. Rollout and fallback guidance for one release cycle.

Acceptance Criteria

  • Markdown/frontmatter validation passes for migrated files.
  • Prompt index and cross-reference links resolve correctly.
  • Representative prompt usage smoke tests are documented.
  • Rollout notes specify fallback behaviour and sunset timing.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Priority

    None yet

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions