flowstate-epic-flowstate-community-epicdm-flowstate-coordinator
Package-local agent skill for @epicdm/flowstate-coordinator.
Tags
Publisher
Versions
1 version published — latest: 1.0.7
- 1.0.7publishedInvalid Date
Skill
flowstate-coordinator Package Skill
Package: @epicdm/flowstate-coordinator
Repository: epic-flowstate-community
Path: packages/flowstate-coordinator
Version: 1.0.7
Use this published Dojo skill as the package-level entrypoint. For detailed workflows, use the package-local skills listed below.
Primary Package Workflow
Coordinator Agent Intelligence
Status: Active
Purpose: Work on optional intelligence subdomains without assuming dependencies are always present.
Scope: wireServices.ts, roundtable, memory, affinity, initiative, voice.
Trigger: Roundtable sessions, memory distillation/injection, affinity scoring, initiative generation, voice profiles, MCP handlers.
Input: Optional LLMClient, optional KnowledgeStoreClient, MCP records, subdomain config.
Output: Correct subdomain behavior or graceful absence.
Subdomains
- Roundtable: sessions, speaker selection, turns, memory integration.
- Memory: distillation and injection with KnowledgeStore.
- Affinity: pairwise relationship records and boosts.
- Initiative: proactive initiative generation and action items.
- Voice: profile/modifier generation and retrieval.
Composition
Use package skills for:
@epicdm/flowstate-agents-llm-client@epicdm/flowstate-agents-knowledge-store
Pitfalls
- Optional clients can be absent; that is normal.
- LLM JSON parse failures often return empty/null rather than throwing.
- Some state is in memory and may not survive restart.
Done When
- Dependency presence/absence is explicit.
- Persisted collections and MCP handlers are checked.
- Tests cover the subdomain behavior touched.
Package Skill Inventory
Package Skill Inventory: @epicdm/flowstate-coordinator
Package Context
Package path: /Users/sthornock/code/epic/epic-flowstate-community/packages/flowstate-coordinator
This package is a large orchestration library and CLI. Skills should mirror coordinator workflows, not the 70+ generated feature/symbol rows.
Skill Map
| Skill | Type | Trigger | Teaches | Evidence | Depends On | Dojo |
|---|---|---|---|---|---|---|
flowstate-coordinator | orchestrator | Use when work touches coordinator service, runtime, exports, docs, or package integration | Routes service, lifecycle, pipeline, clients, subdomains, config, troubleshooting | src/index.ts, src/Coordinator.ts, src/cli.ts | package docs, feature matrix | ready-after-review |
flowstate-coordinator-service-ops | workflow | Use when running or debugging the coordinator CLI/Docker service | CLI startup, health server, MCP wait, org discovery, manager lifecycle, encryption bootstrap | src/cli.ts, CoordinatorManager.ts | MCP server, Docker | ready-after-review |
flowstate-coordinator-agent-lifecycle | workflow | Use when dispatching tasks or handling agent heartbeat/session state | TaskWatcher, HeartbeatMonitor, LifecycleManager, OpenClaw session contracts | source/tests | OpenClaw gateway | ready-after-review |
flowstate-coordinator-work-pipeline | workflow | Use when changing proposal, trigger, mission step, bridge task, approval, or recovery behavior | Gates, ops_policy, triggers, step claim/recovery/reconcile, circuit breaker, approvals | ProposalService, TriggerEvaluator, StepExecutor, ApprovalResolver | flowstate-mcp orchestration tools | ready-after-review |
flowstate-coordinator-client-contracts | reference | Use when wiring MCP HTTP, org scoping, or OpenClaw clients | MCP envelope normalization, org injection, selector limitations, client semantics | clients/*.ts, tests | MCP CRUD contracts | ready-after-review |
flowstate-coordinator-agent-intelligence | workflow | Use when working on roundtable, memory, affinity, initiative, or voice behavior | Service wiring, LLM/KnowledgeStore dependencies, persisted collections, MCP handlers | wireServices.ts, subdomain dirs/tests | LLM client, knowledge-store | ready-after-review |
flowstate-coordinator-config-and-seeds | reference | Use when changing config defaults, env vars, runtime policies, default agents/triggers | ConfigSchema, ConfigRegistry, CONFIG_DEFAULTS, seed records, drift warnings | config/seeds source/tests | ops policy records | ready-after-review |
flowstate-coordinator-troubleshooting | troubleshooting | Use when coordinator behavior disagrees with docs/tests/downstream MCP | VCA filters, stale docs, bridge task reconciliation, optional service absence, adapter risks | tests/docs/reverse refs | all above | local-only |
Anti-Sprawl Decision
Eight skills are appropriate because this package has multiple independent public workflows. Constants, handlers, fixtures, and helper functions are folded into workflow/reference skills rather than becoming standalone skilllets.
Feature Coverage
| Feature Group | Source Evidence | Covered By | Notes |
|---|---|---|---|
| Coordinator/manager/CLI | Coordinator.ts, CoordinatorManager.ts, cli.ts | service-ops, orchestrator | Multi-org behavior |
| Task/lifecycle/heartbeat | TaskWatcher, HeartbeatMonitor, LifecycleManager | agent-lifecycle | Includes OpenClaw |
| Proposal/trigger/steps/approval | ProposalService, TriggerEvaluator, StepExecutor, ApprovalResolver | work-pipeline | Legacy auto-approve caveat |
| MCP/OpenClaw clients | clients/*.ts | client-contracts | Selector and envelope behavior |
| Runtime config/seeds | config.ts, ConfigRegistry, seeds | config-and-seeds | Docs drift |
| Roundtable/memory/affinity/initiative/voice | subdomain dirs, wireServices.ts | agent-intelligence | One composed skill initially |
| Generated Dojo/feature matrix | .flowstate/dojo, .flowstate/feature-matrix | troubleshooting | Do not publish as-is |
Composition Model
Start with the orchestrator. Operational issues go to service-ops. Agent status/task issues go to lifecycle. Proposal/mission work goes to work-pipeline. Transport bugs go to client-contracts. LLM/KnowledgeStore features go to agent-intelligence. Docs/config drift goes to config-and-seeds and troubleshooting.
Deferred Skills
- Approval policy as standalone skill: defer until
ApprovalResolveris wired throughProposalService. - Separate roundtable/memory/affinity/initiative/voice skills: defer until usage proves distinct triggers are needed.
- Observability skill: defer until a distinct operational workflow is reviewed.
- Dojo publishing skill: defer until generated Dojo is rebuilt from reviewed local skills.
Review Questions
- Should
StepExecutorexpose a narrower interface or shouldflowstate-mcpimplementupdateAgentStatus()in its adapter? - Should
ProposalServicemigrate fromauto_approvetoapproval_tiers? - Should package docs be rewritten around current MCP HTTP/multi-org CLI behavior?
Review Gate
Package Skills Review: @epicdm/flowstate-coordinator
Verdict
Pass with fixes.
The local skillset now represents the coordinator as workflow orchestration rather than generated symbols. It captures the major workflow surfaces and the highest-risk cross-package contract issue.
Findings
| Severity | Skill | Issue | Evidence | Required Fix |
|---|---|---|---|---|
| Critical | work-pipeline/troubleshooting | flowstate-mcp StepExecutor adapter may lack updateAgentStatus() for completion release paths | review finding, source contracts | Track/repair before claiming MCP step completion safety |
| Important | all | Existing Dojo content is generated symbol-sprawl | .flowstate/dojo/* | Rebuild from reviewed skills |
| Important | config/service | Docs are stale for modern CLI/MCP HTTP/multi-org behavior | .flowstate/docs, source | Update docs before final Dojo publish |
| Minor | review | Verification passed after authored pass | test, typecheck, build | Keep results with package status before Dojo rebuild |
Coverage
| Feature Group | Status | Skill | Notes |
|---|---|---|---|
| CLI/service/manager | Covered | service-ops | Multi-org + health |
| Task/lifecycle/heartbeat | Covered | agent-lifecycle | Includes OpenClaw |
| Proposal/trigger/step/approval | Covered | work-pipeline | Includes adapter risk |
| MCP/OpenClaw clients | Covered | client-contracts | Envelope/org scoping |
| Config/seeds | Covered | config-and-seeds | Source over stale docs |
| Intelligence subdomains | Covered | agent-intelligence | One composed skill |
| Drift/failures | Covered | troubleshooting | Generated Dojo rejected |
Drift and Contract Risks
| Area | Risk | Evidence | Decision |
|---|---|---|---|
| MCP StepExecutor adapter | Completion can require methods adapter lacks | source/review | Critical follow-up |
| Docs | Old task/config/CLI guidance | docs vs source | Update before publish |
| Dojo | Generated feature skilllets | .flowstate/dojo/* | Rebuild |
| Approval policy | Legacy and newer approval concepts coexist | source TODOs | Track as deferred |
Dojo Publication Decision
Do not publish existing generated Dojo files. Rebuild Dojo artifacts from reviewed local skills after the critical MCP adapter contract is either fixed or explicitly documented as a blocker.
Verification
Commands run:
yarn workspace @epicdm/flowstate-coordinator test
yarn workspace @epicdm/flowstate-coordinator typecheck
yarn workspace @epicdm/flowstate-coordinator build
Results:
- Test passed: 44 suites, 366 tests.
- Typecheck passed.
- Build passed.
Follow-Up Work
- Track/repair MCP
StepExecutoradapter contract. - Update stale package docs.
- Rebuild
.flowstate/dojoartifacts from reviewed skills.
Usage
Start with this skill to understand the package purpose, then use the package-local focused skills for specific workflows. Keep this Dojo version aligned with packages/flowstate-coordinator/package.json. Do not treat generated feature lists as lessons; use workflow evidence from CODE-REVIEW.md, SKILL-INVENTORY.md, and REVIEW.md.
Install
Run this in your project to install via CLI:
fscloud dojo skill install flowstate-epic-flowstate-community-epicdm-flowstate-coordinator --target <target> --out ./skillsReplace <target> with your agent target identifier. See the CLI docs for details.