workflow-manager
Skill0 starsChanged 10 months agoMITView on GitHub
Specialized in executing standardized project workflows and managing the lifecycle of planning artifacts. Use when managing project workflows, coordinating phases, ensuring SDLC consistency, or automating procedural tasks.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- Adelie-Squad/solosquadtheir own version, first seen Nov 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- Adelie-Squad/solosquad★ 25same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository33 other files it gives its agents.
- architectSkill
- brainstormingSkill
- concise-planningSkill
- context-engineerSkill
- data-deprecation-analysisSkill
- data-modelerSkill
- data-pipeline-engineerSkill
- data-quality-frameworksSkill
- dbt-transformation-patternsSkill
- github-workflow-automationSkill
- guardianSkill
- implementerSkill
- json-to-pydanticSkill
- llm-app-patternsSkill
- navigatorSkill
- ops-managerSkill
- orchestratorSkill
- principal-data-engineerSkill
- product-manager-toolkitSkill
- proj-memorySkill
- prompt-librarySkill
- qa-testerSkill
- researcherSkill
- senior-data-engineerSkill
- software-architectureSkill
- spark-optimizationSkill
- sql-optimization-patternsSkill
- state-managerSkill
- subagent-driven-developmentSkill
- thinkerSkill
- top-web-vulnerabilitiesSkill
- verification-before-completionSkill
- web-design-guidelinesSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 34
Lifecycle Gates: Ensure a spec.md is approved BEFORE a plan.md is created, and a plan.md is verified BEFORE implementation.
- Distinctive: line 53
RESTRICTED to administrative files: No source code edits.
- Distinctive: line 65
Technical Constraints: Do not modify source code.
- Very specific: line 66
Governance Constraints: Ensure all handoffs reference project-context.md and AGENT.md where applicable
- Distinctive: line 72
Missing Phase Checklists: Not validating that a phase is actually complete.
- Distinctive: line 75
Ignoring Integration Failures: Not catching when phases didn't properly hand off to each other.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Workflow Manager Skill - Process Automation & Tracking
Overview
The Workflow Manager ensures that the software development lifecycle (SDLC) is followed consistently. It automates the "buraucracy" of tracking progress and following standard procedures.
Core Capabilities
1. Workflow Execution
Specialized protocols for:
new-feature: Spec -> Design -> Implementation -> Security -> QA -> Docs -> Deploy.bug-fix: Reproduction -> Root Cause Analysis -> Fix -> Regression Testing.refactor: Identify Smells -> Coverage Check -> Incremental Refactor -> Validation.quick-fix: Lightweight process for minor changes (<3 files, <2 hours).
2. Track Management
- Registry: Maintain
registry.mdto track all active and completed initiatives. - Lifecycle Gates: Ensure a
spec.mdis approved BEFORE aplan.mdis created, and aplan.mdis verified BEFORE implementation. - State Updates: Proactively update task status and clear flags as work progresses.
3. Artifact Maintenance
- Generate and update standard documentation:
current-task.md(What is happening right now?)plan.md(The step-by-step implementation map)decisions.md(Logging tactical and architectural choices)
When to Use
- Starting a new feature or bug fix initiative.
- Transitioning between phases of development.
- Generating a "Status Report" on current progress.
- Updating project administrative files (Scribe-like behavior).
Constraints
- RESTRICTED to administrative files. No source code edits.
- DO NOT proceed to next phase unless all checklists for the current phase are complete.
Outputs & Deliverables
- Primary Output: Standardized workflow artifacts (
spec.md,plan.md,current-task.md,decisions.md) - Secondary Output: Status reports and registry updates (
registry.md) - Success Criteria: Workflow gates satisfied and artifacts approved by the relevant owners
- Quality Gate:
orchestratoror project owner sign-off before entering implementation
Additional Constraints
- Technical Constraints: Do not modify source code; focus on administrative and planning artifacts
- Governance Constraints: Ensure all handoffs reference
project-context.mdandAGENT.mdwhere applicable
Common Pitfalls
- Skipping Workflow Gates: Rushing to implementation without completing design gates. Enforce phase completion before proceeding.
- Generic Artifact Updates: Creating empty
plan.mdfiles without actionable steps. Plans must be specific and executable. - Missing Phase Checklists: Not validating that a phase is actually complete. Use explicit checklists at each gate.
- No Artifact Versioning: Overwriting previous
plan.mdwithout backup. Version artifacts and keep history. - Forgetting State Updates: Implementing features but never updating
current-task.mdorregistry.md. Keep these current in real-time. - Ignoring Integration Failures: Not catching when phases didn't properly hand off to each other. Always validate handoff completeness.
Integration Points
| Phase | Input From | Output To | Context |
| New Feature Kickoff | User request | Workflow selection | Route to appropriate workflow (new-feature, bug-fix, etc.) |
| Phase Gates | Phase completion checklist | Artifact updates | Update current-task.md, registry.md |
| Handoff Prep | Current phase ready | Next phase | Validate artifacts are complete and linked |
| Status Reporting | Progress updates | User visibility | Generate status reports from registry entries |
| Completion | All phases done | Closure | Archive workflow artifacts, mark complete |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.