sinapse-ai 7.7.3 → 7.7.5

package/.codex/skills/sinapse-qa/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: sinapse-qa
-description: Test Architect & Quality Advisor (Quinn). Use for comprehensive test architecture review, quality gate decisions, and code improvement. Provides thorough analysis including requ...
+description: Test Architect & Quality Advisor (Litmus). Use for comprehensive test architecture review, quality gate decisions, and code improvement. Provides thorough analysis including req...
 ---
 
 # SINAPSE Test Architect & Quality Advisor Activator
@@ -10,19 +10,20 @@ Use for comprehensive test architecture review, quality gate decisions, and code
 
 ## Activation Protocol
 1. Load `.sinapse-ai/development/agents/quality-gate.md` as source of truth (fallback: `.codex/agents/quality-gate.md`).
-2. Adopt this agent persona and command system.
-3. Generate greeting via `node .sinapse-ai/development/scripts/generate-greeting.js qa` and show it first.
-4. Stay in this persona until the user asks to switch or exit.
+2. Generate greeting via `node .sinapse-ai/development/scripts/generate-greeting.js qa` and show it first.
+3. Adopt this agent persona and command system.
+4. If a starred command is invoked in Codex, resolve it via `node .codex/scripts/resolve-codex-command.js sinapse-qa <command>` when a registry mapping exists.
+5. Stay in this persona until the user asks to switch or exit.
 
 ## Starter Commands
 - `*help` - Show all available commands with descriptions
-- `*code-review {scope}` - Run automated review (scope: uncommitted or committed)
-- `*review {story}` - Comprehensive story review with gate decision
-- `*review-build {story}` - 10-phase structured QA review (Epic 6) - outputs qa_report.md
-- `*gate {story}` - Create quality gate decision
-- `*nfr-assess {story}` - Validate non-functional requirements
-- `*risk-profile {story}` - Generate risk assessment matrix
-- `*create-fix-request {story}` - Generate QA_FIX_REQUEST.md for @developer with issues to fix
+- `*code-review` - Run automated review (scope: uncommitted or committed)
+- `*review` - Comprehensive story review with gate decision
+- `*gate` - Create quality gate decision
+- `*nfr-assess` - Validate non-functional requirements
+- `*risk-profile` - Generate risk assessment matrix
+- `*security-check` - Run 8-point security vulnerability scan
+- `*test-design` - Create comprehensive test scenarios
 
 ## Non-Negotiables
 - Follow `.sinapse-ai/constitution.md`.

package/.codex/skills/sinapse-sm/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: sinapse-sm
-description: Scrum Master (River). Use for user story creation from PRD, story validation and completeness checking, acceptance criteria definition, story refinement, sprint planning, backlo...
+description: Scrum Master (Sync). Use for user story creation from PRD, story validation and completeness checking, acceptance criteria definition, story refinement, sprint planning, backlog...
 ---
 
 # SINAPSE Scrum Master Activator
@@ -10,9 +10,10 @@ Use for user story creation from PRD, story validation and completeness checking
 
 ## Activation Protocol
 1. Load `.sinapse-ai/development/agents/sprint-lead.md` as source of truth (fallback: `.codex/agents/sprint-lead.md`).
-2. Adopt this agent persona and command system.
-3. Generate greeting via `node .sinapse-ai/development/scripts/generate-greeting.js sm` and show it first.
-4. Stay in this persona until the user asks to switch or exit.
+2. Generate greeting via `node .sinapse-ai/development/scripts/generate-greeting.js sm` and show it first.
+3. Adopt this agent persona and command system.
+4. If a starred command is invoked in Codex, resolve it via `node .codex/scripts/resolve-codex-command.js sinapse-sm <command>` when a registry mapping exists.
+5. Stay in this persona until the user asks to switch or exit.
 
 ## Starter Commands
 - `*help` - Show all available commands with descriptions

package/.codex/skills/sinapse-squad-creator/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: sinapse-squad-creator
-description: Squad Creator (Craft). Use to create, validate, publish and manage squads
+description: Squad Creator (Loom). Use to create, validate, publish and manage squads
 ---
 
 # SINAPSE Squad Creator Activator
@@ -10,9 +10,10 @@ Use to create, validate, publish and manage squads
 
 ## Activation Protocol
 1. Load `.sinapse-ai/development/agents/squad-creator.md` as source of truth (fallback: `.codex/agents/squad-creator.md`).
-2. Adopt this agent persona and command system.
-3. Generate greeting via `node .sinapse-ai/development/scripts/generate-greeting.js squad-creator` and show it first.
-4. Stay in this persona until the user asks to switch or exit.
+2. Generate greeting via `node .sinapse-ai/development/scripts/generate-greeting.js squad-creator` and show it first.
+3. Adopt this agent persona and command system.
+4. If a starred command is invoked in Codex, resolve it via `node .codex/scripts/resolve-codex-command.js sinapse-squad-creator <command>` when a registry mapping exists.
+5. Stay in this persona until the user asks to switch or exit.
 
 ## Starter Commands
 - `*help` - Show all available commands with descriptions

package/.codex/skills/sinapse-ux-design-expert/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: sinapse-ux-design-expert
-description: UX/UI Designer & Design System Architect (Uma). Complete design workflow - user research, wireframes, design systems, token extraction, component building, and quality assurance
+description: UX/UI Designer & Design System Architect (Mosaic). Complete design workflow - user research, wireframes, design systems, token extraction, component building, and quality assurance
 ---
 
 # SINAPSE UX/UI Designer & Design System Architect Activator
@@ -10,9 +10,10 @@ Complete design workflow - user research, wireframes, design systems, token extr
 
 ## Activation Protocol
 1. Load `.sinapse-ai/development/agents/ux-design-expert.md` as source of truth (fallback: `.codex/agents/ux-design-expert.md`).
-2. Adopt this agent persona and command system.
-3. Generate greeting via `node .sinapse-ai/development/scripts/generate-greeting.js ux-design-expert` and show it first.
-4. Stay in this persona until the user asks to switch or exit.
+2. Generate greeting via `node .sinapse-ai/development/scripts/generate-greeting.js ux-design-expert` and show it first.
+3. Adopt this agent persona and command system.
+4. If a starred command is invoked in Codex, resolve it via `node .codex/scripts/resolve-codex-command.js sinapse-ux-design-expert <command>` when a registry mapping exists.
+5. Stay in this persona until the user asks to switch or exit.
 
 ## Starter Commands
 - `*help` - List available commands

package/.codex/tasks/convene-sinapse-council.md

@@ -0,0 +1,28 @@
+# Codex Council Task
+
+## Purpose
+
+Frame a strategic decision for council-style deliberation in Codex.
+
+## Required Inputs
+
+- Strategic question
+
+## Steps
+
+1. Read `.codex/catalog.json`, `.codex/agents/sinapse-orqx.md`, and `.codex/agents/council-orqx.md`.
+2. Restate the decision in a way that is actionable and falsifiable.
+3. Identify which strategic lenses or squads should weigh in.
+4. Summarize:
+   - core decision
+   - options
+   - tradeoffs
+   - recommended route
+5. If execution needs a concrete framework command, resolve it via `.codex/command-registry.json`.
+
+## Output Contract
+
+- Strategic decision frame
+- Options and tradeoffs
+- Recommended council/orqx route
+- Next action

package/.codex/tasks/create-sinapse-strategic-brief.md

@@ -0,0 +1,29 @@
+# Codex Strategic Brief Task
+
+## Purpose
+
+Generate a Codex-compatible strategic brief that pulls the minimum relevant squads into scope.
+
+## Required Inputs
+
+- Topic or initiative to brief
+
+## Steps
+
+1. Read `.codex/catalog.json` and `.codex/agents/sinapse-orqx.md`.
+2. Classify the topic by domains, urgency, and decision horizon.
+3. Identify the minimum relevant orqx set for the brief.
+4. If the brief depends on a framework workflow step, resolve the starred command via `.codex/command-registry.json`.
+5. Produce a concise brief with:
+   - objective
+   - squads/orqx to involve
+   - key unknowns
+   - risks
+   - recommended next action
+
+## Output Contract
+
+- Strategic brief
+- Recommended squad/orqx set
+- Key risks and unknowns
+- Immediate next step

package/.codex/tasks/onboard-sinapse-codex.md

@@ -0,0 +1,34 @@
+# Codex Onboard Task
+
+## Purpose
+
+Guide the user through the real Codex operating surface for SINAPSE in this repository.
+
+## Required Inputs
+
+- Optional focus area or domain
+
+## Steps
+
+1. Read `AGENTS.md` and `.codex/catalog.json`.
+2. Explain the preferred activation path in Codex:
+   - `/skills` -> `sinapse-<agent>`
+   - `@agent` aliases from `AGENTS.md`
+3. Explain the two Codex layers:
+   - `.codex/skills` for activation
+   - `.codex/agents` for expanded catalog and specialist context
+4. Explain the validated operator commands:
+   - `npm run sync:ide:codex`
+   - `npm run validate:codex-sync`
+   - `npm run validate:codex-integration`
+   - `npm run validate:codex-commands`
+   - `npm run validate:codex-skills`
+   - `npm run validate:paths`
+5. If the user asks how commands map to tasks/workflows, consult `.codex/command-registry.json`.
+6. Tailor the final walkthrough to the requested focus area, if provided.
+
+## Output Contract
+
+- Short explanation of how to activate agents in Codex
+- Short explanation of how workflows/tasks are resolved in Codex
+- Concrete next step for the user based on the requested focus

package/.codex/tasks/plan-sinapse-initiative.md

@@ -0,0 +1,33 @@
+# Codex Plan Task
+
+## Purpose
+
+Produce a Codex-compatible multi-agent execution plan for a complex initiative.
+
+## Required Inputs
+
+- Initiative description
+
+## Steps
+
+1. Read `.codex/catalog.json`.
+2. Break the initiative into domains, risks, and dependencies.
+3. Choose the minimum agent/orqx set required for execution.
+4. For framework workflow steps, resolve commands via `.codex/command-registry.json`.
+5. Structure the plan in phases:
+   - diagnosis
+   - preparation
+   - execution
+   - validation
+6. For each phase, define:
+   - owner agent/orqx
+   - expected artifact or outcome
+   - validation step
+7. Keep the plan Codex-only unless a shared-surface risk is explicitly flagged.
+
+## Output Contract
+
+- Phase-by-phase execution plan
+- Ownership and handoffs
+- Validation gates
+- Shared-surface risks, if any

package/.codex/tasks/resolve-sinapse-conflict.md

@@ -0,0 +1,28 @@
+# Codex Conflict Resolution Task
+
+## Purpose
+
+Resolve cross-squad conflicts or domain overlap without relying on shared-runtime hooks.
+
+## Required Inputs
+
+- Conflict or overlap description
+
+## Steps
+
+1. Read `.codex/catalog.json`, `.codex/agents/sinapse-orqx.md`, and `docs/codex-parity-program.md`.
+2. Identify the squads, agents, or workflow surfaces in conflict.
+3. Separate the problem into:
+   - ownership conflict
+   - sequencing conflict
+   - shared-surface risk
+   - validation gap
+4. Recommend the smallest Codex-safe resolution path.
+5. If a framework command is needed, resolve it through `.codex/command-registry.json`.
+
+## Output Contract
+
+- Conflict diagnosis
+- Recommended owner and route
+- Shared-surface risks, if any
+- Immediate next command or handoff

package/.codex/tasks/route-sinapse-request.md

@@ -0,0 +1,35 @@
+# Codex Route Task
+
+## Purpose
+
+Diagnose a request and choose the smallest correct Codex routing path.
+
+## Required Inputs
+
+- Request description
+
+## Steps
+
+1. Read `.codex/catalog.json`.
+2. Read `.codex/delegation-matrix.json`.
+3. Classify the request as one of:
+   - simple + single-domain
+   - complex + single-domain
+   - complex + multi-domain
+   - framework/development workflow
+4. Prefer the smallest correct path:
+   - simple + single-domain -> relevant `*-orqx` or validated framework agent
+   - complex + single-domain -> relevant `*-orqx`
+   - complex + multi-domain -> `sinapse-orqx` orchestration plan
+   - framework/development workflow -> `sinapse-pm`, `sinapse-po`, `sinapse-sm`, `sinapse-dev`, or `sinapse-qa`
+5. When the request matches an approved handoff route, resolve it through `.codex/delegation-matrix.json`.
+6. If the request depends on a starred command, resolve it through `.codex/command-registry.json`.
+7. Only recommend direct specialist routing from `.codex/agents` when the delegation matrix marks it as `exploratory`.
+8. Return the recommended route with rationale, classification, and next action.
+
+## Output Contract
+
+- Diagnosis
+- Recommended agent or orqx
+- Why that route is correct
+- Immediate next command or handoff

package/.codex/tasks/status-sinapse-capabilities.md

@@ -0,0 +1,28 @@
+# Codex Status Task
+
+## Purpose
+
+Report the validated Codex capability surface for SINAPSE in this repository.
+
+## Steps
+
+1. Read `.codex/catalog.json`.
+2. Summarize:
+   - expanded Codex catalog mode
+   - agent and skill coverage
+   - validated commands available through `.codex/command-registry.json`
+3. Mention the current Codex validation commands:
+   - `npm run validate:codex-sync`
+   - `npm run validate:codex-integration`
+   - `npm run validate:codex-commands`
+   - `npm run validate:codex-skills`
+   - `npm run validate:paths`
+4. If relevant, mention known external blockers outside Codex-only scope:
+   - shared canonical parse issues
+   - non-Codex failures in `validate:parity`
+
+## Output Contract
+
+- Short current-status summary
+- Validated capability list
+- Remaining blockers split into Codex-only vs external/shared

package/.sinapse-ai/core-config.yaml

@@ -192,7 +192,7 @@ github:
         style/: style
         build/: build
       default_type: feat
-    auto_assign_reviewers: false
+    auto_assign_reviewers: true
     draft_by_default: false
   semantic_release:
     enabled: true