---
name: spec-kitty-spk-charter-profile-load
description: "Load a Spec Kitty agent profile on demand for interactive sessions, including identity, governance scope, boundaries, and initialization. Triggers: \"act as the architect\", \"load the reviewer profile\", \"switch to researcher\", \"use the planner role\", \"adopt a profile\"."
license: "MIT"
metadata:
  decimalai-skill-id: "d7f5577a-83cb-4257-a2ce-1734344eb915"
  decimalai-version-id: "f2ad15bc-13ef-44c1-a386-dd677d48b1a0"
  decimalai-version: "1"
  decimalai-body-sha256: "25ac702dd5ba6b7401e583c40b0b4ad3cba2fb505d38350b3b6c0e26489ced7d"
  decimalai-name: "spec-kitty/spk-charter-profile-load"
  decimalai-format: "1"
  decimalai-invocation: "model"
  decimalai-category: "agent-tooling"
  decimalai-source: "https://app.decimal.ai/s/spec-kitty-spk-charter-profile-load@1/SKILL.md"
---
# spk-charter-profile-load

Use this skill when the agent needs a profile outside the runtime loop or the
user asks to adopt a specific role.

## Resolver-Backed Flow

1. Identify the requested profile, action, and active Mission context.
2. Resolve the profile through the CLI:

   ```bash
   spec-kitty agent profile show <profile-id>
   ```

3. Load action-scoped governance:

   ```bash
   spec-kitty charter context --action <action> --json
   ```

4. Apply the resolved initialization declaration, specialization boundaries,
   directive and tactic references, collaboration handoffs, and mode defaults.
5. Return to `spk-run-next` for Mission advancement.

Do not substitute a raw `.agent.yaml` read for resolution. A narrowly scoped
read-only-harness fallback is documented in the reference below.

For a one-shot governed request outside a Mission, use:

```bash
spec-kitty dispatch "<request>" --profile <profile-id>
```

## References

- `references/profile-load-mechanics.md` -- Full resolver flow, application
  checklist, standalone dispatch, and the bounded read-only fallback.