cc-agentic-framework 1.14.1

package/framework/modules/core/skills/committing-code/STANDARDS-FRAMEWORK.md

@@ -0,0 +1,234 @@
+# Managing Git Workflows: Framework Versioning Standards
+
+## Plan-Based Work Format
+
+### Plan Creation Commits
+
+**Pattern:**
+```
+PLAN-<NUMBER>: <Short-Description>
+
+✨ Objective 1 description
+🎯 Objective 2 description
+📋 Objective 3 description
+🔧 Objective 4 description (if applicable)
+
+Plan file: ai/plans/{category}/{number}-{name}/PLAN.md
+Status: 🔶 PROPOSED - PENDING REVIEW
+```
+
+**Rules:**
+- Number: Zero-padded 3 digits (001, 002, 003...)
+- Short-description: 2-4 words, kebab-case style in folder names
+- Emojis: Different emoji per objective/bullet point
+- Each objective: Clear and actionable
+- Plan file location: ai/plans/framework/{number}-{name}/ or ai/plans/apm-r/{number}-{name}/
+- Status: Always include initial status (PROPOSED or IN PROGRESS)
+
+**Example:**
+```
+PLAN-001: Framework consolidation v11.1
+
+✨ Consolidate routes and registry architecture
+🎯 Create shared knowledge skills
+📋 Update all framework references
+🔧 Clean up legacy files
+📚 Document architecture patterns
+
+Plan file: ai/plans/framework/001-consolidation-v11.1/PLAN.md
+Status: 🔶 PROPOSED - PENDING REVIEW
+```
+
+### Phase Execution Commits
+
+**Pattern:**
+```
+PLAN-<NUMBER>-PHASE-<NUMBER>: <Phase-Title>
+
+✅ Deliverable 1 completed
+✅ Deliverable 2 completed
+✅ Deliverable 3 completed
+✅ Deliverable 4 completed (if applicable)
+
+Validation: All success metrics met
+Next phase: PLAN-<NUMBER>-PHASE-<NEXT> ready to start
+```
+
+**Rules:**
+- Plan number: Zero-padded 3 digits (001, 002, 003...)
+- Phase number: Sequential, zero-padded 2 digits (01, 02, 03...)
+- Deliverables: Use ✅ emoji for each concrete deliverable
+- Deliverables: Describe what was actually completed, not what was planned
+- Validation: Note that success metrics were validated
+- Next phase: Indicate readiness for next phase (if applicable)
+- Each commit is atomic: One phase per commit
+
+**Example Phase Commit:**
+```
+PLAN-001-PHASE-01: Create generic skills and infrastructure
+
+✅ Created generic-shared-understanding-framework-architecture-knowledge skill
+✅ Created building-skills skill
+✅ Created ROUTES-REGISTRY-DESIGN.md with complete design rationale
+✅ Updated ai/registry.yml with new skill metadata
+✅ Updated README.md with skill references
+
+Validation: All 4 new skills tested and functional
+Next phase: PLAN-001-PHASE-02 ready (Update framework agents)
+```
+
+### Plan Completion Commits
+
+**Pattern:**
+```
+PLAN-<NUMBER>-COMPLETE: <Plan-Name> - All Phases Done
+
+✅ Phase 1: [description] - COMPLETE
+✅ Phase 2: [description] - COMPLETE
+✅ Phase 3: [description] - COMPLETE
+✅ Phase N: [description] - COMPLETE
+
+Total phases: N (all completed)
+Status file: ai/plans/{category}/{number}-{name}/PROGRESS.md
+Version tag: [if applicable] vX.Y.Z
+
+See: ai/plans/README.md for plan retention policy
+```
+
+**Rules:**
+- Format: `PLAN-{number}-COMPLETE: {Plan-Name} - All Phases Done`
+- List all phases with ✅ emoji and status
+- Include total phase count
+- Reference PROGRESS.md file for detailed tracking
+- If framework version was updated: Include version tag (e.g., v11.1)
+- Include reference to plan retention policy
+
+**Example Completion Commit:**
+```
+PLAN-001-COMPLETE: Framework Consolidation v11.1 - All Phases Done
+
+✅ Phase 1: Create generic skills and infrastructure - COMPLETE
+✅ Phase 2: Update framework agents - COMPLETE
+✅ Phase 3: Clean up legacy documentation - COMPLETE
+✅ Phase 4: Update all references - COMPLETE
+✅ Phase 5: Validation and documentation - COMPLETE
+
+Total phases: 5 (all completed)
+Status file: ai/plans/framework/001-consolidation-v11.1/PROGRESS.md
+Version tag: v11.1
+
+Plan remains in repository as historical record.
+See: ai/plans/README.md for retention policy.
+```
+
+---
+
+## Framework Improvement Format
+
+**Pattern:**
+```
+[vX.Y] <type>: <description>
+```
+
+**Examples:**
+```
+[v11.0] feat: add skills integration
+[v10.1] fix: resolve link validation bug
+[v9.2] docs: update governance rules
+```
+
+**Rules:**
+- Version tag in brackets: `[vX.Y]`
+- Type: feat, fix, refactor, docs, etc.
+- Description: Specific change being made
+- Subject length: Max 50 chars total
+
+## Versioning
+
+**Format:** Semantic versioning
+- `vX.Y.Z` (Major.Minor.Patch)
+- Example: v11.0, v11.0.1, v11.1
+
+**When to bump:**
+- **Major (X):** Breaking changes, large architecture shifts
+- **Minor (Y):** New features, non-breaking additions
+- **Patch (Z):** Bug fixes, small improvements
+
+## Tagging
+
+**Create tag for each version:**
+```bash
+git tag -a v11.0 -m "v11.0: Skills-Based Architecture"
+git push origin --tags
+```
+
+**Tag naming:** `vX.Y.Z` only (no prefix)
+
+## Changelog
+
+**Update format:** Keep consistent with existing
+- List changes by type (Features, Fixes, etc.)
+- Include ticket numbers
+- Include author names
+- Date each version
+
+**Example:**
+```
+## v11.0 (2025-12-04)
+
+### Features
+- Added skills-based specialization architecture
+- Added 2 meta-skills (building-claude-skills, maintaining-framework-governance)
+- Added 3 infrastructure skills (Phase 1B ready)
+
+### Framework Improvements
+- Introduced skills directory structure
+- Set up 2-layer symlink strategy
+- Updated governance rules (6 rules for v11.0)
+
+### Documentation
+- Added v11.0 strategic plan
+- Added completion tracking
+- Added continuation guides
+```
+
+## Commit Checklist for Framework Changes
+
+- [ ] **Version tag included?** [vX.Y]
+- [ ] **Changelog updated?** (if script exists)
+- [ ] **Registry updated?** (if adding features)
+- [ ] **Old version → new version clear?**
+
+## Commit Message Format for Framework
+
+```
+[v<VERSION>] <change-type>: <description>
+
+- Change detail 1
+- Change detail 2
+- Change detail 3
+
+Framework change: v<OLD> → v<NEW>
+Governance rule: Rule X (if applicable)
+```
+
+## Common Mistakes & Fixes
+
+### ❌ Unclear Version Tag
+```
+❌ [version 11] feat: add skills
+✅ [v11.0] feat: add skills
+```
+
+### ❌ No Framework Version Note
+```
+❌ feat: add new skill
+✅ [v11.0] feat: add new skill
+   Framework: v10.0 → v11.0
+```
+
+---
+
+**Standards Category:** Framework Versioning & Tagging
+**Last Updated:** Dec 6, 2025
+**See Also:** [Commit Standards](STANDARDS-COMMITS.md), [Branch Standards](STANDARDS-BRANCHES.md), [Ticket Standards](STANDARDS-TICKETS.md)

package/framework/modules/core/skills/committing-code/STANDARDS-TICKETS.md

@@ -0,0 +1,102 @@
+# Ticket-Based Work Standards
+
+## When to Use Ticket References
+
+Jira ticket references are **automatically detected** from branch names:
+- Branch `DAPM-123-user-auth` → commits use `DAPM-123:` prefix
+- Branch `user-auth` → commits have no prefix
+
+You can also explicitly provide a ticket number when committing.
+
+---
+
+## Ticket Format
+
+**Pattern:** `PROJECT-NUMBER`
+
+**Examples:**
+- `DAPM-123`
+- `PROJ-456`
+- `APMR-789`
+
+**Rules:**
+- Uppercase project code
+- Hyphen separator
+- Numeric ticket number
+
+---
+
+## Commit Format with Ticket
+
+```
+DAPM-123: Short descriptive title
+
+- What was done
+- Another change
+- Additional work
+```
+
+---
+
+## Auto-Detection from Branch
+
+The skill detects Jira tickets by looking for `PROJ-NNN` pattern in branch name:
+
+```bash
+# These branches will auto-prefix commits:
+DAPM-123-user-auth         # → "DAPM-123: ..."
+feature/DAPM-456-login     # → "DAPM-456: ..."
+PROJ-789-export            # → "PROJ-789: ..."
+
+# These will NOT have ticket prefix:
+user-auth-feature          # → "Add user auth..."
+fix-login-bug              # → "Fix login..."
+```
+
+---
+
+## Linking Commits to Tickets
+
+### Primary Method
+Start commit with ticket number:
+```
+DAPM-123: Add user authentication
+```
+
+### Secondary Method (body reference)
+```
+DAPM-123: Add user authentication
+
+- Created login form
+- Added validation
+
+Related: DAPM-124, DAPM-125
+```
+
+---
+
+## Multiple Tickets
+
+When one commit addresses multiple tickets:
+```
+DAPM-123, DAPM-456: Refactor auth module
+
+- Extracted shared utilities
+- Updated both services
+```
+
+---
+
+## Checklist
+
+- [ ] Ticket detected from branch or explicitly provided
+- [ ] Ticket format correct (PROJ-NNN)
+- [ ] Commit title includes ticket prefix
+- [ ] Body describes what was done (3-7 bullets)
+
+---
+
+**See Also:**
+- [SKILL.md](SKILL.md) - Complete git workflow
+- [STANDARDS-COMMITS.md](STANDARDS-COMMITS.md) - Commit format
+- [STANDARDS-BRANCHES.md](STANDARDS-BRANCHES.md) - Branch naming

package/framework/modules/core/skills/gathering-intelligence/SKILL.md

@@ -0,0 +1,136 @@
+---
+id: gathering-intelligence
+module: core
+name: Intelligence Gathering
+description: Dispatch parallel scout sub-agents to gather backlog, codebase, and knowledge context before complex tasks. Use when orchestrator agents need enriched context for ticket creation, implementation, or framework decisions.
+scope: framework
+applicable-projects: any
+capabilities-provided:
+  - intelligence-gathering
+---
+
+# Intelligence Gathering
+
+## When to Use This Skill
+
+You are an **orchestrator agent** about to start a complex task and need enriched context. This skill guides you through dispatching parallel scout sub-agents to gather intelligence before executing your main work.
+
+**Invoke this skill BEFORE starting complex tasks — not after.**
+
+---
+
+## Skip Criteria
+
+Do NOT gather intelligence when:
+- Task is purely mechanical (rename, format, validate, migrate)
+- User explicitly provides all necessary context
+- Task scope is trivial (single file, simple fix, config change)
+- You already have sufficient context from loaded context files
+- Task is a follow-up to work done earlier in the same session
+
+**When in doubt, gather.** The cost of a 30-second parallel scout is far less than the cost of a misaligned deliverable.
+
+---
+
+## Decision Matrix
+
+Use this matrix to determine which scouts to dispatch based on your task type:
+
+| Task Type | Scout: Backlog | Scout: Codebase | Scout: Knowledge |
+|-----------|:-:|:-:|:-:|
+| **Create ticket/epic** | Yes | Yes | Optional |
+| **Decompose epic into stories** | Yes | Yes | No |
+| **Implement feature** | Yes | Yes | Yes |
+| **Fix bug** | No | Yes | Optional |
+| **Refactor code** | No | Yes | Yes |
+| **Framework improvement** | Yes | Yes | Yes |
+| **Governance decision** | Yes | No | Yes |
+| **Module restructuring** | Yes | Yes | Yes |
+| **Write tests** | No | Yes | No |
+| **Design architecture** | Yes | Yes | Yes |
+| **Evaluate tech stack** | Optional | Yes | Yes |
+| **Review/validate** | No | Optional | No |
+| **Documentation update** | No | Optional | Optional |
+| **Create magic system** | No | No | Yes |
+| **Create nation/region** | No | No | Yes |
+| **Create world rule** | No | No | Yes |
+| **Create character** | No | No | Yes |
+| **Create history event** | No | No | Yes |
+| **Plan narrative arc** | No | No | Yes |
+| **Write scene/chapter** | No | No | Yes |
+| **Implement iOS feature** | Yes | Yes | Optional |
+| **Fix iOS bug** | No | Yes | No |
+| **iOS UI redesign** | No | Yes | Yes |
+
+**"Optional"** means: dispatch if the task touches unfamiliar territory or crosses module boundaries. Skip if you're confident in the domain.
+
+---
+
+## Dispatch Instructions
+
+### Step 1: Identify Task Type
+
+Match the user's request to a row in the decision matrix above. If the task spans multiple types, use the row that requires the most scouts.
+
+### Step 2: Dispatch Scouts in Parallel
+
+Use the **Task tool** to dispatch scouts simultaneously. Each scout receives the same task description.
+
+**Dispatch pattern:**
+
+For each scout marked "Yes" in the matrix, create a Task with:
+- **Agent:** The scout's agent file from `framework/modules/core/agents/`
+- **Model:** haiku
+- **Prompt:** Include the task description and any specific search focus
+
+Example dispatch prompt for scout-backlog:
+```
+Task: [paste the user's task description]
+Project: [project name]
+Search focus: [specific domain keywords]
+Graphiti group_id: [from project CLAUDE.md]
+```
+
+**Critical:** Dispatch all scouts in a SINGLE message with multiple Task tool calls. Do NOT dispatch sequentially.
+
+### Step 3: Receive and Review Summaries
+
+Each scout returns a structured summary. Before proceeding:
+1. Read all summaries
+2. Note any contradictions between scouts (e.g., codebase shows pattern X but knowledge says it was deprecated)
+3. Identify the most actionable findings
+4. Discard irrelevant results (scouts sometimes find tangentially related items)
+
+### Step 4: Proceed with Enriched Context
+
+Continue with your main task, informed by the scout summaries. Reference specific findings where relevant:
+- When writing tickets: cite related ticket IDs, align sizing with observed patterns
+- When implementing: follow identified architectural patterns, respect dependency chains
+- When making decisions: reference past decisions and their motivations
+
+---
+
+## Scout Reference
+
+| Scout | Agent File | Purpose |
+|-------|-----------|---------|
+| **ai-scout-backlog** | `framework/modules/core/agents/ai-scout-backlog.md` | Related tickets, sizing patterns, backlog alignment |
+| **ai-scout-codebase** | `framework/modules/core/agents/ai-scout-codebase.md` | Code patterns, architecture, dependencies |
+| **ai-scout-knowledge** | `framework/modules/core/agents/ai-scout-knowledge.md` | Past decisions, historical context, constraints |
+
+---
+
+## After Gathering: Verification Gate
+
+Intelligence gathering is the FIRST step. After synthesizing scout results and executing your main task, you MUST run your domain-specific verification:
+
+| Agent | Verification Skill | Checks |
+|-------|-------------------|--------|
+| ai-backlog-manager | `building-tickets` | YAML frontmatter, Markdown syntax, acceptance criteria, Definition of Ready |
+| ai-app-developer | `verifying-quality` | SOLID/DRY, test coverage, no breaking changes, linter |
+| ai-framework-manager | `building-framework` | Registry consistency, discovery-map, module.json, backward compat |
+| ai-architect | `designing-architecture` | Pattern coherence, constraint satisfaction, trade-off documentation |
+| ai-book-writer | `building-worlds` / `writing-prose` | World consistency, style adherence, continuity |
+| ai-ios-developer | `verifying-quality` | SOLID/DRY, HIG compliance (via ai-hig-reviewer), tests |
+
+**Never skip verification.** Intelligence gathering improves input quality; verification ensures output quality.