Skip to content

guardrails: broader Claude asset migration beyond MVP floor #12

Description

@terisuke

Parent epic: #16

Problem

The MVP floor does not require full migration of every Claude-owned asset, but the longer-term product still needs a principled path for additional skills, commands, and packaging decisions.

Deliverables

  • next-wave migration candidates beyond the MVP floor
  • ownership rules for moving assets from .claude into .opencode
  • packaging and maintenance rules for org-owned assets after the MVP ships

Acceptance

  • the repo distinguishes MVP-critical migration from later migration work
  • future asset moves can point to an explicit issue and ownership rule instead of ad hoc decisions

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