flowstate-epic-flowstate-community-epic-flowstate
Package-local agent skill for epic-flowstate.
Tags
Publisher
Versions
1 version published — latest: 1.0.0
- 1.0.0publishedInvalid Date
Skill
epic-flowstate Package Skill
Package: epic-flowstate
Repository: epic-flowstate-community
Path: .
Version: 1.0.0
Use this published Dojo skill as the package-level entrypoint. For detailed workflows, use the package-local skills listed below.
Primary Package Workflow
Epic FlowState Community Quality Release
Status: Active Purpose: Run quality and release workflows safely in the community monorepo. Scope: Root workspace scripts and package release tooling. Trigger: Use when preparing PRs, releases, package versions, changesets, or broad verification. Input: Change scope, affected packages, package versions, and release intent. Output: Evidence-backed quality/release result.
Workflow
1. Scope The Gate
Use affected package commands when possible. Use root gates when shared contracts or release readiness require them.
2. Run Quality In A Useful Order
Prefer typecheck and focused tests before expensive full builds. Record exact existing failures instead of hiding them.
3. Treat Changesets As Release Artifacts
Use changeset, version-packages, and release only for explicit release work. Do not bump versions to work around Dojo duplicate-version conflicts.
Verification
yarn typecheck
yarn lint
yarn test
yarn build
yarn changeset
Composition
Use package-local skills for package-specific failures. Use package Dojo sync skills when docs, skills, or Dojo manifests changed.
Pitfalls
- Full Nx runs can surface unrelated drift; record it separately.
- Package versions are release authority and should not be changed just to republish documentation.
Done When
The selected gate matches change scope and all failures are either fixed or recorded with source-backed evidence.
Package Skill Inventory
Package Skill Inventory: epic-flowstate
Package Context
The root package skillset teaches agents how to operate the community monorepo safely. It is a workspace skillset, not a replacement for individual package skills.
Skill Map
| Skill | Type | Trigger | Teaches | Evidence | Depends On | Dojo |
|---|---|---|---|---|---|---|
epic-flowstate-community-workspace | orchestrator | Cross-package community repo work | Workspace scripts, package scoping, local services, Dojo sync handoffs | root package.json, packages/*, .flowstate | package-local skills | ready-after-review |
epic-flowstate-community-quality-release | workflow | Running repo-wide gates or release/version workflows | Nx quality gates, changesets, scoped verification, release cautions | root scripts | workspace orchestrator | ready-after-review |
Anti-Sprawl Decision: Two skills are enough because root behavior is coordination. Package features are covered by package-local skills.
Feature Coverage
| Feature Group | Source Evidence | Covered By | Notes |
|---|---|---|---|
| Workspace package routing | root package.json, packages/* | epic-flowstate-community-workspace | Agents should prefer package-local skills after selecting a package. |
| Quality gates | root scripts | epic-flowstate-community-quality-release | Use scoped commands when possible. |
| Docker/local services | root and docker/* scripts | epic-flowstate-community-workspace | Start services only when integration work needs them. |
| Release/version | changeset scripts | epic-flowstate-community-quality-release | Do not version packages casually. |
| Dojo sync | .flowstate package skill/dojos | epic-flowstate-community-workspace | Package-local artifacts remain source of truth. |
Composition Model
Use the workspace orchestrator to choose packages and gates. Then hand off to the affected package-local skills for implementation details.
Deferred Skills
No separate Docker or release reference skill yet; split later if those workflows become too large.
Review Questions
- Should full workspace gate results be captured in a root status ledger after every package-dojo sync?
Review Gate
Package Skills Review: epic-flowstate
Verdict
Pass
Findings
| Severity | Skill | Issue | Evidence | Required Fix |
|---|---|---|---|---|
| Minor | root skillset | Root package is a workspace coordinator, not a runtime package. | root package.json. | Keep root course focused on coordination and route agents to package-local skills. |
Coverage
| Feature Group | Status | Skill | Notes |
|---|---|---|---|
| Workspace operations | Covered | epic-flowstate-community-workspace | Includes package routing. |
| Quality/release gates | Covered | epic-flowstate-community-quality-release | Includes scoped verification. |
| Package Dojo handoff | Covered | epic-flowstate-community-workspace | Keeps package-local source of truth. |
Drift and Contract Risks
| Area | Risk | Evidence | Decision |
|---|---|---|---|
| Root publishability | Root package is private. | package.json. | Publish as workspace course only if catalog should include repo operations; otherwise mark non-publishable during publish. |
Dojo Publication Decision
Ready for local artifact generation. Cloud publish depends on authenticated Dojo session.
Follow-Up Work
- Retry Cloud Dojo publish after cloud auth is repaired.
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 ./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-epic-flowstate --target <target> --out ./skillsReplace <target> with your agent target identifier. See the CLI docs for details.