epicenterhq/workflow
.agents/skills/workflow/SKILL.md
Standard workflow for implementing features with specs and planning documents. Use when the user says "start a new feature", "how should I plan this", "what's the process", or when starting implementation, planning work, or working on any non-trivial task.
$ install --global
skillsauthnpx skillsauth add epicenterhq/epicenter workflowInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 24, 2026, 9:03 PM1.9s1 file scanned
SKILL.md
- name:
- workflow
- description:
- Standard workflow for implementing features with specs and planning documents. Use when the user says "start a new feature", "how should I plan this", "what's the process", or when starting implementation, planning work, or working on any non-trivial task.
- author:
- epicenter
- version:
- 1.0
Standard Workflow
- First think through the problem, read the codebase for relevant files, and write a plan to specs/[timestamp] [feature-name].md where [timestamp] is the timestamp in YYYYMMDDThhmmss format and [feature-name] is the name of the feature.
- The plan should have a list of todo items that you can check off as you complete them
- Before you begin working, check in with me and I will verify the plan. For non-trivial changes (multiple approaches, 3+ files, architecture shifts), present competing options with before/after diffs and ASCII diagrams before implementing (see change-proposal skill).
- Then, begin working on the todo items, marking them as complete as you go.
- Please every step of the way just give me a high level explanation of what changes you made
- Make every task and code change you do as simple as possible. We want to avoid making any massive or complex changes. Every change should impact as little code as possible. Everything is about simplicity.
- Finally, add a review section to the .md file with a summary of the changes you made and any other relevant information.
When to Apply This Skill
Use this pattern when you need to:
- Start a non-trivial feature with a timestamped planning spec in
specs/. - Build a checklist-driven implementation plan before writing code.
- Get plan verification before execution begins.
- Execute work in small, simple steps with high-level progress updates.
- Close work by adding a review summary to the spec.
Spec Placement
All specs live in the root /specs/ directory. Do not create nested specs in apps/ or packages/.
Related Skills
epicenterhq/yjs
documentation
VerifiedTrustedCommunity
Yjs CRDT patterns, shared types (Y.Map, Y.Array, Y.Text), conflict resolution, and document storage. Use when the user mentions Yjs, Y.Doc, CRDTs, collaborative editing, or when handling shared types, implementing real-time sync, or optimizing document storage.
4,428SKILL.mdUpdated Apr 17, 2026
epicenterhq/writing-voice
tools
VerifiedTrustedCommunity
Voice and tone rules for all written content—prose, UI text, tooltips, error messages. Use when the user says "fix the tone", "rewrite this", "sounds like AI", "sounds corporate", or when writing any user-facing text, landing pages, product copy, or open-source documentation.
4,428SKILL.mdUpdated Apr 17, 2026
epicenterhq/workspace-api
tools
VerifiedTrustedCommunity
Workspace API patterns for defineTable, defineKv, versioning, migrations, data access (CRUD + observation), withActions, and extension ordering. Use when the user mentions workspace, defineTable, defineKv, createWorkspace, withActions, withExtension, defineQuery, defineMutation, connectWorkspace, or when defining schemas, reading/writing table data, observing changes, writing migrations, chaining extensions, or attaching actions to a workspace client.
4,428SKILL.mdUpdated Apr 17, 2026
epicenterhq/web-design-guidelines
development
VerifiedTrustedCommunity
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
4,428SKILL.mdUpdated Apr 17, 2026