flowstate-cli Package Skill

Package: @epicdm/flowstate-cli Repository: flowstate-platform Path: packages/cli Version: 0.1.0

Use this published Dojo skill as the package-level entrypoint. For detailed workflows, use the package-local skills listed below.

Primary Package Workflow

CLI Deploy Workflows

Status: Active Purpose: Keep deploy orchestration predictable and testable. Scope: Deploy and start command families in packages/cli. Trigger: Changes to deployment, dependency order, Docker args, warm containers, or service startup. Input: Service name, mode, environment, and deploy config expectations. Output: Tested deploy/start behavior.

Source Map

• src/commands/deploy.ts and src/commands/deploy-all.ts expose runDeploy and runDeployAll.
• src/commands/start.ts resolves local service groups with GROUPS, resolveServices, and runStart.
• src/deploy-config.ts loads config, resolves services, and computes dependency order.
• src/deploy-docker.ts builds Docker args and backup/warm-container paths.
• src/warm-container.ts starts, stops, and executes deploy work in a warm container.

Workflow

1. Start in tests: deploy.test.ts, deploy-all.test.ts, deploy-config.test.ts, deploy-docker.test.ts, or start.test.ts.
2. Update exported helpers before CLI wrappers so behavior remains unit-testable.
3. Keep dry-run behavior free of remote side effects.
4. If dependency ordering changes, update resolveDependencyOrder coverage.
5. If Docker args change, assert exact argv arrays in tests.

Verification

• yarn workspace @epicdm/flowstate-cli test src/__tests__/deploy.test.ts src/__tests__/deploy-all.test.ts src/__tests__/deploy-docker.test.ts
• yarn workspace @epicdm/flowstate-cli typecheck

Created: 2026-06-30

Package Skill Inventory

Skill Inventory: @epicdm/flowstate-cli

Review date: 2026-06-30

Composition Notes

Start with flowstate-cli-operations, then choose deploy, secrets, or smoke/Dojo based on the command family.

Review Gate

Package Skills Review: @epicdm/flowstate-cli

Review date: 2026-06-30 Status: Pass for local agent use

Checks

• Skills are based on command source, supporting libraries, and test files.
• Descriptions use trigger conditions instead of workflow summaries.
• Infrastructure and secret-handling risks are called out explicitly.
• Files were written only under packages/cli/.flowstate/skills.

Pressure Scenario

Scenario: "Add a dry-run deploy flag that also affects deploy-all."

Expected behavior with skills: load flowstate-cli-operations and flowstate-cli-deploy; inspect DeployOptions, DeployAllOptions, config resolution, Docker args, and tests in deploy*.test.ts before changing command output.

Remaining Risk

Some commands invoke Docker, Wrangler, OP, or networked Dojo APIs. Prefer unit tests and dry-run paths in this package unless the user explicitly asks for live operations.

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/cli/package.json. Do not treat generated feature lists as lessons; use workflow evidence from CODE-REVIEW.md, SKILL-INVENTORY.md, and REVIEW.md.