Skip to content

[Epic] Prompt library scope classification and migration governance #736

@ashleyshaw

Description

@ashleyshaw

Template source: .github/ISSUE_TEMPLATE/05-epic.md\nTemplate label: 📦 Epic\nSpec source: .github/projects/active/refactor-migrate-prompts/openspec-strict/parents/01-epic-prompt-library-scope-and-migration-governance.md\n\n---\n## Template Base\n\n

Epic Summary

Linked Stories/Tasks

Milestones & Timeline

Acceptance Criteria

  • All linked stories/tasks completed
  • Documentation and changelog updated
  • Tests/QA complete
  • Milestone closed

Dependencies / Blockers

Additional Context


Definition of Ready (DoR)

  • Epic goal and scope defined
  • Linked stories/tasks listed
  • Milestones and timeline mapped
  • Dependencies/blockers identified
  • Estimate added (if applicable)
  • Stakeholders/approvers listed

Definition of Done (DoD)

  • All linked stories/tasks completed and closed
  • Documentation/changelog updated
  • QA and testing complete
  • Milestone closed and release notes prepared

---\n\n---\n## Spec Details\n\n## template-map

  • template_file: .github/ISSUE_TEMPLATE/05-epic.md

Overview

Define and execute the migration strategy for prompt assets between .github/prompts/ and root prompts/.

Goals

  1. Establish canonical prompt boundaries.
  2. Execute migration with explicit mapping, refactoring, and validation.
  3. Prevent path breakage with deprecation guidance and updated indexes.

Acceptance Criteria

  • Final prompt matrix approved.
  • Approved move set refactored to root standard.
  • References and discoverability updated in both prompt directories.
  • Validation completed for formatting, links, and smoke usage paths.

Child Issues

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