OpenArc

Use when a new goal, feature request, migration, or non-trivial change needs focused clarification before PRD, spec, plan, or implementation work begins.

Use when implementing repository changes through the smallest safe path, from direct routine fixes to risk-driven clarification, specs, plans, task coordination, validation, and documentation updates.

Use when a user asks to use OpenArc generally, initialize governance, improve repository continuity, audit governance drift, migrate an existing workspace, or choose which OpenArc skill should handle a request.

Use when producing a lightweight implementation plan before coding, including scope, affected systems, migration, rollback, tests, reuse, and architecture impact.

Use when auditing repository governance read-only, or when explicitly initializing or repairing governance and patching an agent guide without destructive rewrites.

Use when creating or updating OpenArc feature specs with acceptance criteria, compatibility decisions, and technical direction.

Use when a user proposes changes that may require patch, minor, or major version changes, release notes, changelog updates, or version confirmation.

Use when migrating an existing repository or workspace into OpenArc conventions, aligning docs, specs, plans, assets, agent guides, versions, and release workflow without destructive rewrites.

Use when cutting or merging branches, making commits, opening pull requests, preparing release notes, or triggering GitHub release updates in an OpenArc-governed repository.

Use when creating or maintaining docs/DESIGN.md as the implementation-facing source of truth for UI, layout, component, accessibility, and interaction rules.

Use when creating or maintaining docs/PRD.md, product requirements, product scope, user stories, success metrics, or product source-of-truth documents for OpenArc repositories.

Use when maintaining AI-assisted change memory, CHANGELOG_AI.md, docs/archive, historical context retention, archive indexes, or context-budget-aware repository reading in OpenArc repositories.

Use when creating or maintaining OpenArc asset structure under docs/assets for brand files, icons, illustrations, screenshots, and references.

Use when creating or maintaining docs/BRAND.md as the brand-facing source of truth for tone, identity, naming, copy, storytelling, and visual direction.

Use when preparing OpenArc or an OpenArc-governed repository for public open-source release, contribution readiness, license alignment, changelog hygiene, or public README cleanup.