# Skills organization and naming

**Status:** Agreed direction from discussion. Migration is not yet authorized.

## Decisions

- **Corp will be rebranded as SKIC.**
- Organizations use **scope first**, followed by `-skills`.
- Skill names use **capability first**, followed by scope and project suffixes.
- **Global skills have no suffix.**
- Projects can have their own skills organization.
- Repository name, installed skill folder, and declared skill name should match.

## Naming examples

| Organization | Skill / repository name |
|---|---|
| `global-skills` | `development-gates` |
| `home-skills` | `development-gates-home` |
| `skic-skills` | `development-gates-skic` |
| `skic-aerosim-skills` | `development-gates-skic-aerosim` |

**Organization:** `<scope>[-<project>]-skills`

**Skill:** `<capability>[-<scope>][-<project>]`

For global skills, omit scope and project from the skill name.

## Why this approach

- Organizations group skills by ownership and project.
- Skill names group variants by capability when cloned side by side.
- Global → workstream → project expresses increasing specialization, not automatic copying or inherited approval.

```text
development-gates
development-gates-home
development-gates-skic
development-gates-skic-aerosim
```

## Boundaries

- Create a scoped variant when it needs different rules or context; do not clone every global skill into every organization.
- The organization list can grow with workstreams and projects; no fixed total is decided.
- Existing organizations and skills remain unchanged until migration is separately approved.
- Detailed maintenance and approval rules remain a separate discussion.
