---
name: {PROJECT_KEY_LOWERCASE}:confluence
version: "0.7.4"
description: Confluence page management for the {CONFLUENCE_SPACE_KEY} space
disable-model-invocation: false
---

# Confluence Skill

Config-only skill — manage Confluence pages in the <CONFLUENCE_SPACE_KEY> space. Action: $ARGUMENTS

---

## Visual Framework

Follow the visual framework defined in the `output:visual-framework` primitive.

---

## Usage

```bash
/{PROJECT_KEY_LOWERCASE}:confluence create "Page Title" --label specapi    # Create a labeled page
/{PROJECT_KEY_LOWERCASE}:confluence search "authentication"                # Search space for pages
/{PROJECT_KEY_LOWERCASE}:confluence label 12345 accepted specfeat           # Add labels to a page
```

## Space Constants

- Space Key: <CONFLUENCE_SPACE_KEY>
- Space ID: <CONFLUENCE_SPACE_ID>
- Homepage ID: <CONFLUENCE_HOMEPAGE_ID>

## Label Taxonomy

### Status Labels (mutually exclusive)

- `accepted` - Reviewed and active, synced to agent context
- `draft` - Work in progress, not synced
- `superseded` - Replaced by a newer document, not synced
- `deprecated` - No longer relevant, not synced

### Type Labels

- `architecture` - System architecture docs
- `prd` - Product requirements
- `datamodel` - Data model documentation
- `specapi` - API specifications
- `specfeat` - Feature specifications
- `specdesign` - Design specifications
- `specdata` - Data specifications
- `adr` - Architecture Decision Records
- `llm` - LLM/AI-specific specs
- `specifications` - Spec index pages

## Rules

- **MUST** add both a status label AND a type label on every page operation. Do NOT create or update a page without both label types.
- Use `accepted` for pages that agents MUST reference
- Page titles MUST follow: "<PROJECT_NAME> - {Title}" for top-level, "SPEC-<TYPE>-<NUM>: {Title}" for specs
