orchestrator

Imported from markromolecule/context-factory (orchestrator/AGENTS.md). Install upstream with npx skills add markromolecule/context-factory --skill orchestrator. Copyright stays with the author.

Context Factory Entry Point & Agent Dispatch Contract

Read orchestrator/SHARED.md before changing this factory or using it to guide project work. Treat context-manifest.json as the canonical inventory.

Mandatory Directives (MUST)

• MUST: Read orchestrator/SHARED.md and consult context-manifest.json as the canonical inventory.
• MUST: Deterministically resolve required context before executing non-trivial requests by running node scripts/context.mjs resolve "<user request>" or checking the Trigger Dispatch Matrix below.
• MUST: Inspect and load applicable rules from rules/ matching the touched files and domain:
  • Global rules: rules/global/ (1-3-1-rule.md, code-quality.md, evidence-and-claims.md, security-guardrails.md, naming-conventions.md, architecture-conformance.md, git-commit.md).
  • SOLID rules: rules/solid/ (single-responsibility.md, open-closed.md, liskov-substitution.md, interface-segregation.md, dependency-inversion.md).
  • TypeScript rules: rules/typescript/common/ (type-safety.md, runtime-validation.md, error-handling.md, async-discipline.md, module-and-imports.md, next-react-project-structure.md).
  • Database rules: rules/typescript/database/ (schema-db.md, data-access-via-db.md, query-optimization-and-pagination.md, testing-data-access-layer.md).
  • Backend rules: rules/typescript/backend/ (module-architecture.md, controllers-and-routes.md, service-layer.md, data-access-via-api.md).
  • Hooks rules: rules/typescript/hooks/ (custom-hooks.md, query-hooks.md, mutation-hooks.md, zustand-store.md).
  • UI rules: rules/typescript/ui/ (frontend.md, code-organization.md, forms-and-validation.md, dialogs-and-overlays.md, interaction-feedback.md).
• MUST: Route multi-stage engineering lifecycles to the appropriate workflow from workflows/ (feature-delivery.md, defect-resolution.md, database-migration.md, security-sensitive-change.md, architecture-change.md, context-maintenance.md, dependency-upgrade.md, release-readiness.md).
• MUST: Activate and read the matching skill under skills/<skill_name>/SKILL.md whenever user request mentions or matches skill trigger concepts.
• MUST: Activate skills/grill/SKILL.md before planning when working on a new system, product, or materially ambiguous feature.
• MUST: Activate skills/plan/SKILL.md for task breakdowns, plans, and design proposals; output to docs/tasks/ using docs/templates/Task.md & Phase.md. Stop before coding.
• MUST: Activate skills/execute/SKILL.md when executing approved phase tasks, working strictly one phase at a time with developer review stops.
• MUST: Follow vertical backend module boundaries and prevent layer leaking (rules/typescript/backend/module-architecture.md).
• MUST: Ground claims using canonical knowledge under knowledge/ (skills/grounding/SKILL.md).
• MUST: Verify claims with fresh, reproducible test evidence before reporting completion (rules/global/evidence-and-claims.md, skills/verify/SKILL.md).
• MUST: Run node scripts/context.mjs lock and node scripts/context.mjs doctor after modifying context rules, skills, workflows, or templates.

Trigger & Skill Dispatch Matrix

When any user request mentions or matches these concepts, immediately activate and follow the corresponding skill:

Session Slash Commands & Prefix Triggers

When the user's prompt begins with a slash command or bracket prefix, prioritize the matching workflow and subagent:

Workflow Routing

For multi-stage engineering lifecycles, load the appropriate workflow from workflows/:

• New Project & Greenfield Delivery: workflows/new-project-delivery.md
• New Feature Delivery: workflows/feature-delivery.md
• Code Review & Optimization: workflows/code-review-and-optimization.md
• Commit, Push & Release: workflows/commit-push-release.md
• Bug & Defect Fixes: workflows/defect-resolution.md
• Database & Schema Changes: workflows/database-migration.md
• Security Changes: workflows/security-sensitive-change.md
• Architecture Refactoring: workflows/architecture-change.md
• Context Maintenance: workflows/context-maintenance.md
• Dependency Upgrades: workflows/dependency-upgrade.md
• Release Readiness: workflows/release-readiness.md

Coding Lifecycle Subagents

When addressing lifecycle-specific phases, adopt or delegate to the corresponding subagent from agents/:

• Business Analyst (agents/ba-agent/AGENT.md): Use for requirements discovery, user stories, domain terms, and scenario matrices (/ba).
• Architect & ADR Specialist (agents/architect-agent/AGENT.md): Use for system boundaries, dependency direction, SOLID principles, and durable ADRs (/architect).
• Data Modeler (agents/data-agent/AGENT.md): Use for database schemas, ESR indexing, migrations, rollback runbooks, and data access isolation (/data).
• Project Manager (agents/pm-agent/AGENT.md): Use for phased task plans, milestone tracking, and blocker resolution (/pm).
• UX & Design System Specialist (agents/ux-agent/AGENT.md): Use for accessible UI components, design tokens, interaction feedback, and custom hooks (/ux).
• Security & Threat Specialist (agents/threat-agent/AGENT.md): Use for STRIDE threat modeling, trust boundaries, secrets hygiene, and adversarial security gates (/threat).
• DevOps Specialist (agents/devops-agent/AGENT.md): Use for CI/CD pipelines (.github/workflows/), Docker containerization, environment hygiene (.env.example), and release readiness (/devops).

Context Maintenance

After making changes to factory rules, skills, workflows, or templates:

1. Run node scripts/context.mjs lock
2. Run node scripts/context.mjs doctor