sinapse-ai 7.1.0 → 7.2.0

package/squads/claude-code-mastery/workflows/wf-knowledge-update.yaml

@@ -0,0 +1,165 @@
+# ============================================================================
+# Workflow: Knowledge Update
+# Squad: claude-code-mastery
+# Version: 1.0.0
+# Purpose: Refresh squad knowledge from Claude Code changelog and roadmap
+# ============================================================================
+
+workflow:
+  id: wf-knowledge-update
+  name: "Claude Code Knowledge Update"
+  version: "1.0.0"
+  description: |
+    Workflow to refresh the claude-code-mastery squad's knowledge base
+    from official Claude Code sources: changelog, documentation, blog posts,
+    and community resources. Ensures the squad stays current.
+
+  trigger: "*update-knowledge"
+  entry_agent: roadmap-sentinel
+  estimated_duration: "15-30 minutes"
+
+# ────────────────────────────────────────────────────────────────────────────
+# PHASES
+# ────────────────────────────────────────────────────────────────────────────
+
+phases:
+
+  # ─── PHASE 0: Source Collection ──────────────────────────────────────────
+  - id: phase_0
+    name: "Source Collection"
+    agent: roadmap-sentinel
+    description: |
+      Fetch latest information from all official and community sources.
+    steps:
+      - "Fetch Claude Code CHANGELOG.md from GitHub"
+      - "Fetch latest releases from GitHub releases page"
+      - "Check official documentation at code.claude.com/docs"
+      - "Check Anthropic blog for Claude Code announcements"
+      - "Check community sources (claudelog.com, claudefast.com)"
+    sources:
+      changelog: "https://github.com/anthropics/claude-code/blob/main/CHANGELOG.md"
+      releases: "https://github.com/anthropics/claude-code/releases"
+      docs: "https://code.claude.com/docs/en/overview"
+      blog: "https://claude.com/blog/"
+      community:
+        - "https://claudelog.com/claude-code-changelog/"
+        - "https://claudefa.st/blog/guide/changelog"
+    outputs:
+      - latest_version: "string (e.g., 1.0.47)"
+      - new_features: "array of feature descriptions"
+      - breaking_changes: "array (if any)"
+      - deprecations: "array (if any)"
+    checkpoint:
+      gate: "At least changelog and releases fetched successfully"
+      veto: "No sources accessible (network issue)"
+
+  # ─── PHASE 1: Delta Analysis ────────────────────────────────────────────
+  - id: phase_1
+    name: "Delta Analysis"
+    agent: roadmap-sentinel
+    depends_on: [phase_0]
+    description: |
+      Compare new information against squad's current knowledge base
+      to identify what needs updating.
+    steps:
+      - "Read current data/claude-code-quick-ref.yaml"
+      - "Compare tool list, hook events, features against latest docs"
+      - "Identify new features not in knowledge base"
+      - "Identify deprecated features still in knowledge base"
+      - "Assess impact on each specialist agent"
+    outputs:
+      - delta_report:
+          new_features: "array"
+          deprecated_features: "array"
+          changed_features: "array"
+          affected_agents: "array of agent IDs"
+      - update_priority: "string (critical | important | minor | none)"
+    checkpoint:
+      gate: "Delta report generated"
+      veto: "If update_priority is 'none', skip remaining phases"
+
+  # ─── PHASE 2: Knowledge Base Update ─────────────────────────────────────
+  - id: phase_2
+    name: "Knowledge Base Update"
+    agent: roadmap-sentinel
+    depends_on: [phase_1]
+    description: |
+      Update the squad's data files with new information.
+    steps:
+      - "Update data/claude-code-quick-ref.yaml with new features"
+      - "Update data/hook-patterns.yaml if new hook events"
+      - "Update data/mcp-integration-catalog.yaml if new MCPs"
+      - "Add new entries to relevant data files"
+      - "Remove deprecated entries"
+    outputs:
+      - files_updated: "array of file paths"
+      - entries_added: "number"
+      - entries_removed: "number"
+    checkpoint:
+      gate: "All identified deltas addressed in data files"
+      veto: "Removing entries without deprecation notice"
+
+  # ─── PHASE 3: Agent Impact Assessment ───────────────────────────────────
+  - id: phase_3
+    name: "Agent Impact Assessment"
+    agent: claude-mastery-chief
+    depends_on: [phase_2]
+    description: |
+      Assess which specialist agents need updates based on the delta.
+    steps:
+      - "For each affected agent, identify impacted sections"
+      - "Check if agent's knowledge references are still accurate"
+      - "Flag agents that need quick_reference or commands updates"
+      - "Generate update recommendations per agent"
+    outputs:
+      - agent_updates:
+          - agent_id: "string"
+            sections_affected: "array"
+            priority: "string (critical | recommended | optional)"
+            recommendation: "string"
+    checkpoint:
+      gate: "All affected agents assessed"
+      veto: "N/A (assessment only)"
+
+  # ─── PHASE 4: Summary & Notification ────────────────────────────────────
+  - id: phase_4
+    name: "Update Summary"
+    agent: claude-mastery-chief
+    depends_on: [phase_3]
+    description: |
+      Generate final update summary with actionable next steps.
+    steps:
+      - "Compile update summary"
+      - "List all changes made"
+      - "List recommended agent updates"
+      - "Provide version comparison (was → now)"
+    outputs:
+      - update_report:
+          version_before: "string"
+          version_after: "string"
+          data_files_updated: "number"
+          agents_needing_update: "number"
+          summary: "string"
+
+# ────────────────────────────────────────────────────────────────────────────
+# COMPLETION CRITERIA
+# ────────────────────────────────────────────────────────────────────────────
+
+completion_criteria:
+  - "All official sources checked"
+  - "Delta report generated"
+  - "Knowledge base data files updated"
+  - "Agent impact assessment completed"
+  - "Update summary report generated"
+
+# ────────────────────────────────────────────────────────────────────────────
+# SCHEDULE
+# ────────────────────────────────────────────────────────────────────────────
+
+schedule:
+  recommended: "Run after each Claude Code version update"
+  minimum: "Monthly"
+  trigger_on:
+    - "User runs *update-knowledge or *updates"
+    - "Claude Code version change detected"
+    - "User asks 'what is new in Claude Code?'"

package/squads/claude-code-mastery/workflows/wf-project-setup.yaml

@@ -0,0 +1,192 @@
+# ============================================================================
+# Workflow: Project Setup
+# Squad: claude-code-mastery
+# Version: 1.0.0
+# Purpose: Full Claude Code project setup from zero to production-ready
+# ============================================================================
+
+workflow:
+  id: wf-project-setup
+  name: "Claude Code Project Setup"
+  version: "1.0.0"
+  description: |
+    End-to-end workflow to set up Claude Code in any project.
+    Orchestrates config-engineer, hooks-architect, mcp-integrator,
+    and project-integrator to create a complete, production-ready setup.
+
+  trigger: "*setup-project"
+  entry_agent: claude-mastery-chief
+  estimated_duration: "30-60 minutes"
+
+# ────────────────────────────────────────────────────────────────────────────
+# PHASES
+# ────────────────────────────────────────────────────────────────────────────
+
+phases:
+
+  # ─── PHASE 0: Discovery ───────────────────────────────────────────────────
+  - id: phase_0
+    name: "Discovery & Detection"
+    agent: project-integrator
+    task: integrate-project.md
+    description: |
+      Detect project type, analyze existing structure, determine what
+      Claude Code components are needed.
+    steps:
+      - "Scan project root for signature files (package.json, requirements.txt, Cargo.toml, etc.)"
+      - "Match against project-type-signatures.yaml"
+      - "Detect existing Claude Code setup (partial? none?)"
+      - "Determine setup scope: greenfield vs brownfield"
+    outputs:
+      - project_type: "string (monorepo | fullstack-nextjs | react-library | python-api | ...)"
+      - existing_setup: "object (has_claude_dir, has_settings, has_claudemd, has_hooks, has_mcp)"
+      - setup_scope: "string (greenfield | brownfield | upgrade)"
+    checkpoint:
+      gate: "Project type detected with confidence >= 0.7"
+      veto: "If project type undetectable, ask user to specify"
+
+  # ─── PHASE 1: CLAUDE.md Engineering ──────────────────────────────────────
+  - id: phase_1
+    name: "CLAUDE.md Engineering"
+    agent: project-integrator
+    task: claude-md-engineer.md
+    depends_on: [phase_0]
+    description: |
+      Generate an optimized CLAUDE.md tailored to the detected project type.
+    steps:
+      - "Select template from templates/ based on project_type"
+      - "Analyze project structure for conventions (naming, patterns, tools)"
+      - "Generate CLAUDE.md under 200 lines"
+      - "Add managed sections for auto-update capability"
+    outputs:
+      - claude_md_path: ".claude/CLAUDE.md or CLAUDE.md"
+      - line_count: "number (target: < 200)"
+    checkpoint:
+      gate: "CLAUDE.md exists, < 200 lines, has essential sections"
+      veto: "CLAUDE.md > 500 lines without user approval"
+
+  # ─── PHASE 2: Configuration ──────────────────────────────────────────────
+  - id: phase_2
+    name: "Settings & Permissions"
+    agent: config-engineer
+    task: configure-claude-code.md
+    depends_on: [phase_0]
+    description: |
+      Generate .claude/settings.json with appropriate permissions,
+      deny rules, and MCP server configurations.
+    steps:
+      - "Generate .claude/settings.json with deny-first approach"
+      - "Configure permission mode based on project needs"
+      - "Add deny rules for sensitive files (.env, secrets, credentials)"
+      - "Configure allow rules for common safe operations"
+    outputs:
+      - settings_path: ".claude/settings.json"
+      - permission_mode: "string"
+      - deny_rules_count: "number"
+    checkpoint:
+      gate: "settings.json valid, deny rules cover .env and secrets"
+      veto: "No deny rules for sensitive files"
+
+  # ─── PHASE 3: Rules ─────────────────────────────────────────────────────
+  - id: phase_3
+    name: "Conditional Rules"
+    agent: config-engineer
+    task: create-rules.md
+    depends_on: [phase_1]
+    description: |
+      Create .claude/rules/ with path-based conditional rules
+      to keep context window lean.
+    steps:
+      - "Identify rule categories (testing, API, database, frontend, etc.)"
+      - "Create rules with paths: frontmatter for conditional loading"
+      - "Move detailed instructions from CLAUDE.md to rules"
+      - "Validate rules load correctly"
+    outputs:
+      - rules_dir: ".claude/rules/"
+      - rules_count: "number"
+    checkpoint:
+      gate: "At least 2 rules created with valid frontmatter"
+      veto: "Rules without paths: frontmatter (always-loaded bloat)"
+
+  # ─── PHASE 4: Hooks ─────────────────────────────────────────────────────
+  - id: phase_4
+    name: "Hook Setup"
+    agent: hooks-architect
+    task: hook-designer.md
+    depends_on: [phase_2]
+    description: |
+      Configure hooks for the project based on its needs.
+    steps:
+      - "Assess hook needs from project type and workflow"
+      - "Create damage-control hook (block dangerous commands)"
+      - "Optionally add auto-lint, notification, or cost-tracking hooks"
+      - "Add hooks to settings.json"
+      - "Test hook execution"
+    outputs:
+      - hooks_configured: "number"
+      - hook_types: "array of event names"
+    checkpoint:
+      gate: "At least damage-control hook configured and tested"
+      veto: "Hook with syntax errors in settings.json"
+
+  # ─── PHASE 5: MCP Servers ───────────────────────────────────────────────
+  - id: phase_5
+    name: "MCP Integration"
+    agent: mcp-integrator
+    task: mcp-workflow.md
+    depends_on: [phase_2]
+    description: |
+      Configure MCP servers appropriate for the project's tech stack.
+    steps:
+      - "Map project needs to available MCP servers"
+      - "Calculate context budget impact"
+      - "Configure essential MCPs (prioritize by ROI)"
+      - "Test tool availability with ToolSearch"
+    outputs:
+      - mcp_servers: "array of configured servers"
+      - context_budget_used: "number (tokens)"
+    checkpoint:
+      gate: "MCP servers configured and responding"
+      veto: "Context budget > 10K tokens for MCP tools alone"
+
+  # ─── PHASE 6: Validation ────────────────────────────────────────────────
+  - id: phase_6
+    name: "Setup Validation"
+    agent: claude-mastery-chief
+    task: audit-setup.md
+    depends_on: [phase_1, phase_2, phase_3, phase_4, phase_5]
+    description: |
+      Run full audit of the completed setup to ensure quality.
+    steps:
+      - "Execute *audit command"
+      - "Verify all components are properly configured"
+      - "Generate setup report with score"
+      - "Recommend next steps"
+    outputs:
+      - audit_score: "number (0-100)"
+      - grade: "string (A-F)"
+      - recommendations: "array"
+    checkpoint:
+      gate: "Audit score >= 70 (grade C or better)"
+      veto: "Score < 50 — fundamental setup issues"
+
+# ────────────────────────────────────────────────────────────────────────────
+# COMPLETION CRITERIA
+# ────────────────────────────────────────────────────────────────────────────
+
+completion_criteria:
+  - "CLAUDE.md exists and is < 200 lines"
+  - ".claude/settings.json is valid with deny rules"
+  - "At least 2 conditional rules in .claude/rules/"
+  - "At least 1 hook configured (damage-control minimum)"
+  - "MCP servers configured for project stack"
+  - "Audit score >= 70"
+
+# ────────────────────────────────────────────────────────────────────────────
+# VETO CONDITIONS (workflow-level)
+# ────────────────────────────────────────────────────────────────────────────
+
+veto_conditions:
+  - "No .env or secrets files accessible without deny rules"
+  - "No autoApprove permission mode without explicit user consent"
+  - "No MCP configuration that exceeds context budget"