### Getting Started Tutorial Structure

Source: https://github.com/priivacy-ai/spec-kitty/blob/main/kitty-specs/014-comprehensive-end-user-documentation/tasks/WP03-tutorials.md

This markdown structure outlines the 'getting-started.md' tutorial, guiding new users through installation and project initialization.

```markdown
# Getting Started with Spec Kitty

In this tutorial, you'll install Spec Kitty and create your first feature specification.

**Time**: ~30 minutes
**Prerequisites**: Python 3.11+, Git, an AI coding agent (Claude Code, etc.)

## Step 1: Install Spec Kitty
[pip/uv installation commands]

## Step 2: Initialize a Project
[spec-kitty init commands]

## Step 3: Create Your First Specification
[/spec-kitty.specify walkthrough]

## Step 4: Verify Your Work
[Check kitty-specs/ directory]

## What's Next?
[Links to your-first-feature.md, how-to guides]
```

--------------------------------

### Link to Initial Setup Documentation

Source: https://github.com/priivacy-ai/spec-kitty/blob/main/kitty-specs/023-documentation-sprint-agent-management-cleanup/tasks/WP03-manage-agents-how-to-supplementary.md

Include this Markdown to link to the installation guide, focusing on the initial agent selection process during `spec-kitty init`.

```markdown
### Initial Setup

- [Installing spec-kitty](install-spec-kitty.md) - Initial agent selection during `spec-kitty init`
```

--------------------------------

### Full Interactive CLI Setup

Source: https://github.com/priivacy-ai/spec-kitty/blob/main/src/doctrine/skills/spec-kitty-charter-doctrine/references/charter-command-map.md

Guides through a comprehensive interactive CLI setup for project charter generation.

```bash
spec-kitty charter interview --mission-type software-dev --profile comprehensive
spec-kitty charter generate --from-interview
```

--------------------------------

### Complete Spec Kitty Workflow Example

Source: https://context7.com/priivacy-ai/spec-kitty/llms.txt

An end-to-end example demonstrating the Spec Kitty workflow using the `next` runtime loop, from installation and initialization to accepting and merging changes.

```bash
# 1. Install and initialize
pip install spec-kitty-cli
spec-kitty init my-app --ai claude
cd my-app

# 2. In your AI agent: establish governance charter (one-time per project)
# /spec-kitty.charter

# 3. In your AI agent: create spec
# /spec-kitty.specify Build a REST API for a task management system.

# 4. In your AI agent: create technical plan
# /spec-kitty.plan Use FastAPI, PostgreSQL, Docker. JWT auth.

# 5. In your AI agent: generate work packages
# /spec-kitty.tasks

# 6. (Optional) Cross-artifact analysis
# /spec-kitty.analyze

# 7. Run the agent loop from the terminal
MISSION="001-task-management-api"
while true; do
  DECISION=$(spec-kitty next --agent claude --mission "$MISSION" --json)
  ACTION=$(echo "$DECISION" | python3 -c "import sys,json; d=json.load(sys.stdin); print(d.get('action','done'))")
  WP=$(echo "$DECISION" | python3 -c "import sys,json; d=json.load(sys.stdin); print(d.get('wp_id',''))")

  case "$ACTION" in
    implement)
      spec-kitty agent action implement "$WP" --agent claude
      # Claude does the implementation work in the lane worktree...
      spec-kitty next --agent claude --mission "$MISSION" --result success --json
      ;;
    review)
      spec-kitty agent action review "$WP" --agent claude
      # Claude reviews the work...
      spec-kitty next --agent claude --mission "$MISSION" --result success --json
      ;;
    done|complete)
      echo "Mission $MISSION is complete"
      break
      ;;
    *)
      echo "Unhandled action: $ACTION"
      break
      ;;
  esac
done

# 8. Accept and merge
spec-kitty accept --mission "$MISSION" --test "pytest tests/" --json
spec-kitty merge --strategy SQUASH --push
```

--------------------------------

### Example Pipeline Setup and Usage

Source: https://github.com/priivacy-ai/spec-kitty/blob/main/kitty-specs/041-mission-glossary-semantic-integrity/contracts/middleware.md

Demonstrates how to instantiate a GlossaryMiddlewarePipeline with various middleware components and how to process an initial context, handling potential exceptions.

```python
pipeline = GlossaryMiddlewarePipeline([
    GlossaryCandidateExtractionMiddleware(extraction_config),
    SemanticCheckMiddleware(glossary_store),
    GenerationGateMiddleware(strictness_policy),
    ClarificationMiddleware(interaction_mode),
    ResumeMiddleware(checkpoint_store)
])

try:
    final_context = pipeline.process(initial_context)
    # All checks passed - proceed to generation
except BlockedByConflict:
    # Generation blocked - clarification required
except DeferredToAsync:
    # User deferred resolution - exit
```

--------------------------------

### Add Cross-Reference to Install Guide

Source: https://github.com/priivacy-ai/spec-kitty/blob/main/kitty-specs/023-documentation-sprint-agent-management-cleanup/tasks/WP06-cross-reference-updates.md

This markdown snippet should be added to `docs/how-to/install-spec-kitty.md` to guide users on managing agents post-initialization.

```markdown
### Managing Agents After Initialization

After running `spec-kitty init`, you can add or remove agents at any time using the `spec-kitty agent config` command family.

To manage agents post-init:
- **Add agents**: `spec-kitty agent config add <agents>`
- **Remove agents**: `spec-kitty agent config remove <agents>`
- **Check status**: `spec-kitty agent config status`

See [Managing AI Agents](manage-agents.md) for complete documentation on agent management workflows.
```

--------------------------------

### Multi-Agent Setup Command

Source: https://github.com/priivacy-ai/spec-kitty/blob/main/kitty-specs/014-comprehensive-end-user-documentation/tasks/WP07-reference-config.md

Example command to initialize a project with multiple AI agents selected.

```bash
spec-kitty init my-project --ai claude,codex
```

--------------------------------

### Alternative Simpler Note for Install Guide

Source: https://github.com/priivacy-ai/spec-kitty/blob/main/kitty-specs/023-documentation-sprint-agent-management-cleanup/tasks/WP06-cross-reference-updates.md

A concise alternative note for `docs/how-to/install-spec-kitty.md` if a simpler cross-reference is preferred.

```markdown
> **Managing agents after init**: To add or remove agents later, see [Managing AI Agents](manage-agents.md).
```

--------------------------------

### Copilot CLI Version and Path

Source: https://github.com/priivacy-ai/spec-kitty/blob/main/research/02-github-copilot.md

Example output showing the Copilot CLI version, commit hash, and installation path.

```bash
$ copilot --version
0.0.384
Commit: 0b21260

$ which copilot
/opt/homebrew/bin/copilot
```

--------------------------------

### Quickstart: Real Example - This Feature

Source: https://github.com/priivacy-ai/spec-kitty/blob/main/kitty-specs/010-workspace-per-work-package-for-parallel-development/tasks/WP10-documentation-and-migration-guide.md

Demonstrates the new workspace-per-work-package model by showing the commands used to build the feature itself. It covers both the planning phase in the main repository and the implementation phase where worktrees are created for individual work packages.

```bash
# Ran in main repository
/spec-kitty.specify "Workspace-per-Work-Package for Parallel Development"
→ Created kitty-specs/010-workspace-per-work-package-for-parallel-development/spec.md
→ Committed to main
→ NO worktree created

/spec-kitty.plan
→ Created plan.md in main
→ Committed to main

/spec-kitty.tasks
→ Created 10 WP files in main
→ Generated dependencies in frontmatter
→ Committed to main

```

```bash
# WP01 - Foundation
spec-kitty implement WP01
→ Created .worktrees/010-workspace-per-wp-WP01/
→ Branched from main

# WP02, WP03, WP06 - Parallel development (Wave 2)
spec-kitty implement WP02 --base WP01
spec-kitty implement WP03 --base WP01  # Parallel with WP02!
spec-kitty implement WP06               # Independent, parallel!

# Three agents worked simultaneously on WP02, WP03, WP06

```

--------------------------------

### Get Efficient Local Tooling Toolguide

Source: https://github.com/priivacy-ai/spec-kitty/blob/main/src/doctrine/skills/spec-kitty-charter-doctrine/SKILL.md

Retrieve a toolguide for operational guidance on specific tools. This example shows how to get the 'efficient-local-tooling' guide.

```python
toolguide = service.toolguides.get("efficient-local-tooling")
```

--------------------------------

### Complete Governance Setup Workflow

Source: https://github.com/priivacy-ai/spec-kitty/blob/main/docs/how-to/setup-governance.md

A comprehensive example demonstrating the initial setup of Spec Kitty governance for a new project, including project initialization, interview, charter generation, status verification, and starting a workflow.

```bash
# 1. Create the Spec Kitty project scaffold
uv run spec-kitty init --ai claude --non-interactive

# 2. Run the interview
uv run spec-kitty charter interview \
  --profile comprehensive

# 3. Generate charter and extracted config
uv run spec-kitty charter generate --from-interview --json

# 4. Verify everything is in sync
uv run spec-kitty charter status --json

# 5. Start working -- governance context loads automatically
uv run spec-kitty specify "Build user authentication module"
```

--------------------------------

### Vibe CLI Next Steps Instructions

Source: https://github.com/priivacy-ai/spec-kitty/blob/main/kitty-specs/083-agent-skills-codex-vibe/tasks/WP05-vibe-cli-surface.md

Provides specific instructions for users when the selected agent is Vibe, guiding them through installation and initial workflow setup.

```python
    if agent_key == "vibe":
        print("Next steps for Mistral Vibe:")
        print("  1. Install Vibe if you haven\'t already:")
        print("     curl -LsSf https://mistral.ai/vibe/install.sh | bash")
        print("   or")
        print("     uv tool install mistral-vibe")
        print("  2. Launch Vibe in this project:")
        print("     vibe")
        print("  3. Inside Vibe, invoke your first workflow:")
        print("     /spec-kitty.specify <describe what you want to build>")
```

--------------------------------

### Example with Options

Source: https://github.com/priivacy-ai/spec-kitty/blob/main/src/specify_cli/missions/documentation/templates/divio/reference-template.md

Illustrates how to use a command or API with various options.

```text
```{language}
{example-with-options}
```
```

--------------------------------

### CI Workflow SSH Setup

Source: https://github.com/priivacy-ai/spec-kitty/blob/main/architecture/adrs/2026-01-27-11-dual-repository-pattern.md

Example of setting up an SSH deploy key in a CI workflow before installing dependencies. This is crucial for accessing private Git repositories.

```yaml
steps:
  - uses: actions/checkout@v3
  - name: Set up SSH deploy key
    env:
      SPEC_KITTY_EVENTS_DEPLOY_KEY: ${{ secrets.SPEC_KITTY_EVENTS_DEPLOY_KEY }}
    run: |
      mkdir -p ~/.ssh
      echo "$SPEC_KITTY_EVENTS_DEPLOY_KEY" > ~/.ssh/id_rsa
      chmod 600 ~/.ssh/id_rsa
  - name: Install dependencies
    run: poetry install
```

--------------------------------

### PowerShell Commands for Windows Dashboard Testing

Source: https://github.com/priivacy-ai/spec-kitty/blob/main/kitty-specs/011-constitution-packaging-safety-and-redesign/tasks/WP06-integration-testing-validation.md

This PowerShell script demonstrates the steps to install the spec-kitty CLI, initialize a test project, start and stop the dashboard, and verify its status. It includes commands for installation, project setup, dashboard interaction, and process verification.

```powershell
# On Windows machine
pip install .\dist\spec_kitty_cli-*.whl

# Create test project
cd C:\test
git init
spec-kitty init

# Start dashboard
spec-kitty dashboard
# Expected: "Dashboard starting on http://127.0.0.1:9237"

# Open browser to http://127.0.0.1:9237
# Expected: Kanban board loads, no ERR_EMPTY_RESPONSE

# Test with curl (PowerShell)
Invoke-WebRequest http://127.0.0.1:9237
# Expected: StatusCode 200, Content.Length > 0

# Stop dashboard
spec-kitty dashboard --stop
# Expected: "Dashboard stopped"

# Verify process gone
Get-Process | Where-Object {$_.Name -like "*dashboard*"}
# Expected: Empty
```

--------------------------------

### Good Tutorial Example (Linking to Reference)

Source: https://github.com/priivacy-ai/spec-kitty/blob/main/docs/explanation/divio-documentation.md

A good tutorial focuses on the user's task and links to reference documentation for command details. This keeps the tutorial concise and actionable.

```markdown
# Getting Started

Run `spec-kitty init` to set up your project.
For all available options, see the [CLI Reference](../reference/cli-commands.md#spec-kitty-init).
```

--------------------------------

### Local Test Results with Gemini CLI

Source: https://github.com/priivacy-ai/spec-kitty/blob/main/research/03-google-gemini.md

Example output from verifying the Gemini CLI installation and running a basic command. Note the authentication error indicating setup is required.

```bash
$ which gemini
/opt/homebrew/bin/gemini

$ gemini --version
0.24.0

$ echo 'print("Hello")' | gemini -p "What does this code do?" --output-format json
{
  "session_id": "b2b90938-611f-4bd0-adf6-829e14549653",
  "error": {
    "type": "Error",
    "message": "Please set an Auth method in your ~/.gemini/settings.json...",
    "code": 41
  }
}
```

--------------------------------

### Example Bash Command in Tutorial

Source: https://github.com/priivacy-ai/spec-kitty/blob/main/kitty-specs/012-documentation-mission/tasks/WP03-divio-templates.md

An example of a command to be included in a tutorial step. Ensure the command is exact and includes any necessary flags and arguments.

```bash
command --with-flags argument
```

--------------------------------

### Verify pytestarch installation

Source: https://github.com/priivacy-ai/spec-kitty/blob/main/kitty-specs/058-mission-template-repository-refactor/tasks/WP10-architectural-dependency-tests.md

Verify that pytestarch can be imported and used after installation. This confirms the setup is correct.

```python
python -c "from pytestarch import get_evaluable_architecture; print('OK')"
```

--------------------------------

### Update Getting Started Docs

Source: https://github.com/priivacy-ai/spec-kitty/blob/main/kitty-specs/079-post-555-release-hardening/plan.md

Update approximately 12 getting-started documentation files to replace mentions of top-level `spec-kitty implement` in their initial paragraphs. These updates should focus on the canonical path, introducing `spec-kitty next` as the loop and `spec-kitty agent action implement/review` as per-WP actions, while leaving references in troubleshooting sections untouched if they describe the command as an internal detail.

```markdown
Canonical path: `spec-kitty next` (loop), `spec-kitty agent action implement`, `spec-kitty agent action review`
```

--------------------------------

### Example: All 13 Init-Surface Agents

Source: https://github.com/priivacy-ai/spec-kitty/blob/main/docs/how-to/non-interactive-init.md

Initializes a new project with all 13 available init-surface AI agents enabled in non-interactive mode. This demonstrates a comprehensive setup.

```bash
spec-kitty init my-project \
  --ai codex,claude,gemini,cursor,qwen,opencode,windsurf,kilocode,auggie,roo,copilot,q,kiro \
  --non-interactive
```

--------------------------------

### Modified Command for Different Setup

Source: https://github.com/priivacy-ai/spec-kitty/blob/main/src/doctrine/missions/documentation/templates/divio/howto-template.md

Modify the command as shown if you are using a different setup than the primary example.

```bash
{modified version}
```

--------------------------------

### Create Initial Project Documentation

Source: https://github.com/priivacy-ai/spec-kitty/blob/main/docs/explanation/documentation-mission.md

Use this command to initiate comprehensive documentation for a new project, specifying iteration mode, Divio types, target audience, and generators.

```bash
# In your project root
cd kitty-specs/ 
/spec-kitty.specify Create comprehensive documentation for our project, covering all four Divio types
```

```bash
/spec-kitty.plan We'll use Sphinx for Python API docs, organize by feature modules
```

```bash
/spec-kitty.tasks
```

```bash
/spec-kitty.implement
```

--------------------------------

### Verify Sphinx Installation

Source: https://github.com/priivacy-ai/spec-kitty/blob/main/src/doctrine/missions/documentation/templates/plan-template.md

Command to check if Sphinx is installed and retrieve its version. Useful for verifying setup.

```bash
sphinx-build --version
```

--------------------------------

### Verify JSDoc Installation

Source: https://github.com/priivacy-ai/spec-kitty/blob/main/src/doctrine/missions/documentation/templates/plan-template.md

Command to check if JSDoc is installed and retrieve its version. Useful for verifying setup.

```bash
npx jsdoc --version
```

--------------------------------

### Run Agent Mission Setup Plan Help

Source: https://github.com/priivacy-ai/spec-kitty/blob/main/kitty-specs/charter-end-user-docs-828-01KQCSYD/research.md

Displays help information for the agent mission setup-plan command.

```bash
agent mission setup-plan --help
```

--------------------------------

### Good How-To Example (Focused on Action)

Source: https://github.com/priivacy-ai/spec-kitty/blob/main/docs/explanation/divio-documentation.md

A good how-to guide provides clear, actionable steps to achieve a goal. It links to explanations for theoretical background.

```markdown
# How to Resolve Merge Conflicts

1. Identify conflicting files: `git status`
2. Open each file and find `<<<<<<<` markers
3. Choose which changes to keep
4. Remove conflict markers
5. Stage and commit: `git add . && git commit`

For background on why conflicts occur, see [Git Worktrees Explained](../explanation/git-worktrees.md).
```

--------------------------------

### Install JSDoc and Template

Source: https://github.com/priivacy-ai/spec-kitty/blob/main/docs/explanation/documentation-mission.md

Install JSDoc and the 'docdash' template as development dependencies. This setup is required before generating JavaScript/TypeScript documentation.

```bash
npm install --save-dev jsdoc docdash
```

--------------------------------

### Implement 'setup-plan' Entry Gate

Source: https://github.com/priivacy-ai/spec-kitty/blob/main/kitty-specs/charter-e2e-827-followups-01KQAJA0/plan.md

Add a check at the beginning of 'setup-plan' to ensure 'spec.md' is committed and substantive. If not, emit a 'blocked' status and return without processing 'plan.md'.

```python
# In mission.py, around line 973
# Check is_substantive(spec_path, "spec") AND that spec.md is committed
# If either fails, emit phase_complete=False / blocked_reason="spec.md must be committed and substantive before plan phase" and return
```

--------------------------------

### Execute Quickstart Commands

Source: https://github.com/priivacy-ai/spec-kitty/blob/main/kitty-specs/034-feature-status-state-model-remediation/tasks/WP17-documentation-and-final-report.md

Run these commands sequentially to validate the quickstart.md documentation. Each command tests a specific aspect of the agent status functionality.

```bash
spec-kitty agent status migrate --feature 099-quickstart-test
```

```bash
spec-kitty agent status emit WP01 --to claimed --actor test
```

```bash
spec-kitty agent status materialize --feature 099-quickstart-test
```

```bash
spec-kitty agent status validate --feature 099-quickstart-test
```

```bash
spec-kitty agent status doctor --feature 099-quickstart-test
```

```bash
spec-kitty agent status reconcile --feature 099-quickstart-test --dry-run
```

--------------------------------

### Install Agent CLI for 'Agent Not Found' Error

Source: https://github.com/priivacy-ai/spec-kitty/blob/main/kitty-specs/020-autonomous-multi-agent-orchestrator/quickstart.md

If you encounter an 'Agent Not Found' error, install the specific agent's CLI using npm. This example shows how to install the Claude Code agent.

```bash
npm install -g @anthropic-ai/claude-code
```

--------------------------------

### Example Migration: Ensure Missions

Source: https://github.com/priivacy-ai/spec-kitty/blob/main/kitty-specs/012-documentation-mission/tasks/WP08-migration.md

This example migration demonstrates how to ensure missions are present in the project. It can be used as a reference for implementing the documentation mission installation.

```python
from src.specify_cli.upgrade.migrations.base import BaseMigration
from src.specify_cli.upgrade.registry import MigrationRegistry

@MigrationRegistry.register
class EnsureMissionsMigration(BaseMigration):
    migration_id = "m_0_6_7_ensure_missions"
    description = "Ensures core missions are present."
    target_version = "0.6.7"

    def detect(self) -> bool:
        # Detect if missions are present
        pass

    def apply(self) -> None:
        # Apply logic to ensure missions
        pass
```

--------------------------------

### Check Claude Code CLI Version and Path

Source: https://github.com/priivacy-ai/spec-kitty/blob/main/research/01-claude-code.md

Example output showing the version and installation path of the Claude Code CLI after successful installation.

```bash
$ claude --version
2.1.12 (Claude Code)
```

```bash
$ which claude
~/.local/bin/claude
```

--------------------------------

### Configuration File Example

Source: https://github.com/priivacy-ai/spec-kitty/blob/main/CLAUDE.md

Example of a config.yaml file defining available agents for the project.

```yaml
agents:
  available:
    - opencode
    - claude
```

--------------------------------

### Initialize and Run Documentation Mission

Source: https://github.com/priivacy-ai/spec-kitty/blob/main/kitty-specs/documentation-mission-composition-rewrite-01KQ5M1Y/quickstart.md

This sequence sets up a temporary repository, initializes a documentation mission using `spec-kitty` CLI, and inspects the mission details. Ensure to use `--project` with `uv` to avoid corrupting the source repository.

```bash
# 1. Set absolute paths.
SPEC_KITTY_REPO="/path/to/spec-kitty"   # <-- the merged spec-kitty repo
TMP_REPO="$(mktemp -d -t docs-smoke-XXXXXX)/repo"

# 2. Initialize a fresh temp repo OUTSIDE the spec-kitty source tree (C-010).
mkdir -p "$TMP_REPO"
cd "$TMP_REPO"
git init --initial-branch=main >/dev/null
git config user.email "smoke@test.local"
git config user.name  "Smoke"
echo "# smoke repo" > README.md
git add README.md
git commit -m "init" >/dev/null

# 3. Create a documentation mission via the spec-kitty CLI from the temp repo.
#    Use --project (not --directory) per #735.
uv run --project "$SPEC_KITTY_REPO" \
    spec-kitty agent mission create demo-docs --mission-type documentation --json \
    > create.json

# 4. Inspect the mission_id / mission_slug.
MISSION_HANDLE="$(python3 -c 'import json; print(json.load(open("create.json"))["mission_slug"])')"
echo "mission handle: ${MISSION_HANDLE}"
```

--------------------------------

### How-To Guide Example Structure

Source: https://github.com/priivacy-ai/spec-kitty/blob/main/docs/explanation/documentation-mission.md

This markdown structure is for task-oriented guides that solve specific problems. It assumes some familiarity and provides a step-by-step solution with verification.

```markdown
# How to Configure OAuth Authentication

## Problem
You need to add OAuth authentication to your application.

## Prerequisites
- Existing application setup
- OAuth provider credentials

## Solution

### Step 1: Install Dependencies
```bash
pip install authlib
```

### Step 2: Configure Provider
...

### Step 3: Implement Login Flow
...

## Verification
Test your OAuth flow by...

## Troubleshooting
- **Error: Invalid redirect URI** - Check your...
```

--------------------------------

### Example Bash Command in How-To Template

Source: https://github.com/priivacy-ai/spec-kitty/blob/main/kitty-specs/012-documentation-mission/tasks/WP03-divio-templates.md

An example of a bash command within a how-to guide step, intended to be replaced with a specific command for the task.

```bash
# Command or code example
command --option value
```

--------------------------------

### Initial Project Documentation - Review and Accept

Source: https://github.com/priivacy-ai/spec-kitty/blob/main/docs/explanation/documentation-mission.md

Commands to review the generated documentation and formally accept it.

```bash
/spec-kitty.review
/spec-kitty.accept
```

--------------------------------

### Tutorial Example Structure

Source: https://github.com/priivacy-ai/spec-kitty/blob/main/docs/explanation/documentation-mission.md

This markdown structure is used for creating learning-oriented tutorials. It assumes no prior knowledge and guides the user through a complete, working example.

```markdown
# Getting Started with [Project]

## What You'll Build
By the end of this tutorial, you'll have a working...

## Prerequisites
- Python 3.11+
- Basic command line knowledge

## Step 1: Installation
First, install the package...

## Step 2: Your First [Feature]
Now let's create...

## Next Steps
You've learned the basics. Next, explore...
```

--------------------------------

### Initial Project Documentation - Implement

Source: https://github.com/priivacy-ai/spec-kitty/blob/main/docs/explanation/documentation-mission.md

Command to implement the generated documentation tasks, creating configuration files, content, and updating the README.

```bash
/spec-kitty.implement
```

--------------------------------

### Get Implementer Agent Profile

Source: https://github.com/priivacy-ai/spec-kitty/blob/main/src/doctrine/skills/spec-kitty-charter-doctrine/SKILL.md

Retrieve an agent profile, which defines role specifications. This example shows how to get the 'implementer' profile and access its properties.

```python
profile = service.agent_profiles.get("implementer")
# profile.purpose.mandate → what this agent is responsible for
# profile.specialization.boundaries → what it should not do
```

--------------------------------

### Extract and run documentation code examples

Source: https://github.com/priivacy-ai/spec-kitty/blob/main/kitty-specs/041-mission-glossary-semantic-integrity/tasks/WP11-type-safety-and-integration-tests.md

This is a placeholder comment indicating a task to extract code examples from documentation (quickstart.md) and validate them. Actual execution would require a custom script or manual verification.

```bash
# Extract code examples from quickstart.md and run them
# (manual verification or custom script)
```

--------------------------------

### Bad Tutorial Example (Mixed with Reference)

Source: https://github.com/priivacy-ai/spec-kitty/blob/main/docs/explanation/divio-documentation.md

Avoid mixing tutorial content with detailed command-line flag documentation. Link to reference material instead for comprehensive flag details.

```markdown
# Getting Started

Run `spec-kitty init`. This command accepts the following flags:
--force, --quiet, --verbose, --config=PATH, --mission=TYPE...
[100 lines of flag documentation]
```

--------------------------------

### Table of Contents for 0.12.0 Upgrade Guide

Source: https://github.com/priivacy-ai/spec-kitty/blob/main/kitty-specs/023-documentation-sprint-agent-management-cleanup/tasks/WP04-migration-guide-012.md

Example table of contents for a new markdown file detailing the 0.12.0 upgrade, providing links to key sections within the guide.

```markdown
## Contents

- [What Changed](#what-changed)
- [Why This Change](#why-this-change)
- [Migration Steps](#migration-steps)
- [Troubleshooting](#troubleshooting)
- [See Also](#see-also)

```

--------------------------------

### Append Section to Existing Upgrade Guide

Source: https://github.com/priivacy-ai/spec-kitty/blob/main/kitty-specs/023-documentation-sprint-agent-management-cleanup/tasks/WP04-migration-guide-012.md

Example of how to append the 0.12.0 upgrade content as a new section to an existing upgrade guide file, using a horizontal rule for separation.

```markdown
---

## Upgrading to 0.12.0

[Same content as above]

```