Individual skill
project-flow-ops
Use when projects or tasks need explicit state, WIP control, ownership, definitions of done, blocker handling, and verified closure.
skills/project-flow-ops/SKILL.md
Source commit 5a645148a108d71c76521715117b737ae60b1423
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 4, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 140
- Repository last updated
- Sep 19, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude-skills Repository topic
- agentic Repository topic
- ai-agents Repository topic
- cursor-rules Repository topic
- knowledge-management Repository topic
- obsidian Repository topic
- codex Repository topic
- ontology Repository topic
- loop Repository topic
- loop-engineering Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 4,336 bytes
Read excerpt
# Project Flow Ops
<skill_contract>
<input>Project objective, tasks, owners, dependencies, budgets, artifacts, current states, and definitions of done.</input>
<output>A WIP-limited project state with ranked work, explicit blockers, bounded actions, and verified closure receipts.</output>
<done>Every active item has one owner and observable artifact, and completion is backed by its named fresh verification.</done>
<non_goals>Hidden WIP, duplicate ownership, status by intuition, backlog accumulation, or completion without evidence.</non_goals>
Maintain a small, inspectable project state machine: `BACKLOG -> ACTIVE -> BLOCKED | COMPLETED`. Optimize flow and verified outcomes, not task volume.
## Usage Template
Provide: project objective, current tasks, owners, dependencies, time budget, artifacts, and definition of done. Optional: prior review receipts.