Knowledge Ops
affaan-m/ECC
Knowledge base management, ingestion, sync, and retrieval across multiple storage layers (local files, MCP memory, vector stores, Git repos).
A skill your agent uses when projects or tasks need explicit state, WIP control, ownership, definitions of done, blocker handling, and verified closure.
MITAuto-check passed
Install Project Flow Ops
$ npx skills add Mark393295827/third-brain-v7-skills --skill project-flow-ops -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Mark393295827/third-brain-v7-skills project-flow-ops --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Mark393295827/third-brain-v7-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/project-flow-ops .claude/skills/project-flow-ops && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "project-flow-ops" agent skill from https://github.com/Mark393295827/third-brain-v7-skills/tree/main/skills/project-flow-ops into .claude/skills/project-flow-ops/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "project-flow-ops", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Mark393295827/third-brain-v7-skills/tree/main/skills/project-flow-opsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Mark393295827/third-brain-v7-skills --skill project-flow-ops -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Mark393295827/third-brain-v7-skills project-flow-ops --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Mark393295827/third-brain-v7-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/project-flow-ops .agents/skills/project-flow-ops && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "project-flow-ops" agent skill from https://github.com/Mark393295827/third-brain-v7-skills/tree/main/skills/project-flow-ops into .agents/skills/project-flow-ops/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "project-flow-ops", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Mark393295827/third-brain-v7-skills --skill project-flow-ops -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Mark393295827/third-brain-v7-skills project-flow-ops --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Mark393295827/third-brain-v7-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/project-flow-ops .cursor/skills/project-flow-ops && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "project-flow-ops" agent skill from https://github.com/Mark393295827/third-brain-v7-skills/tree/main/skills/project-flow-ops into .cursor/skills/project-flow-ops/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "project-flow-ops", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Mark393295827/third-brain-v7-skills.git --path skills/project-flow-ops--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Mark393295827/third-brain-v7-skills --skill project-flow-ops -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Mark393295827/third-brain-v7-skills project-flow-ops --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Mark393295827/third-brain-v7-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/project-flow-ops .gemini/skills/project-flow-ops && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "project-flow-ops" agent skill from https://github.com/Mark393295827/third-brain-v7-skills/tree/main/skills/project-flow-ops into .gemini/skills/project-flow-ops/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "project-flow-ops", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Mark393295827/third-brain-v7-skills project-flow-opsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Mark393295827/third-brain-v7-skills --skill project-flow-ops -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Mark393295827/third-brain-v7-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/project-flow-ops .github/skills/project-flow-ops && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "project-flow-ops" agent skill from https://github.com/Mark393295827/third-brain-v7-skills/tree/main/skills/project-flow-ops into .github/skills/project-flow-ops/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "project-flow-ops", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Mark393295827/third-brain-v7-skills --skill project-flow-ops -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Mark393295827/third-brain-v7-skills project-flow-ops --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Mark393295827/third-brain-v7-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/project-flow-ops .opencode/skills/project-flow-ops && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "project-flow-ops" agent skill from https://github.com/Mark393295827/third-brain-v7-skills/tree/main/skills/project-flow-ops into .opencode/skills/project-flow-ops/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "project-flow-ops", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
project-flow-ops- GitHub stars
- 141
- Token cost
- ~1.1k tokens
- SKILL.md length
- 503 words
- Files
- 1
- Skills in repo
- 21
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when projects or tasks need explicit state, WIP control, ownership, definitions of done, blocker handling, and verified closure.
- Works in 7 steps: Rank work by objective impact, urgency,… → Limit ACTIVE to one or two items per… → Decompose the selected item until one… → …
- Tasks need explicit state
- SKILL.md covers Usage Template, Workflow, Failure Protocol and Output Contract, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Project Flow Ops is an agent skill from Mark393295827/third-brain-v7-skills. Use when projects or tasks need explicit state, WIP control, ownership, definitions of done, blocker handling, and verified closure.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: agent wiki +engineering skills. The licence is MIT.
When your agent uses it
- Tasks need explicit state
- Definitions of done
- Blocker handling
- Verified closure
Example prompts
- “/project-flow-ops”
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Rank work by objective impact, urgency, dependency leverage, and cost of delay.
- Limit ACTIVE to one or two items per owner.
- Decompose the selected item until one bounded action can produce a reviewable artifact.
- For a blocker, record owner, missing condition, evidence, next probe, and review time; move independent work forward.
- Run the verification named in the definition of done.
- Move to COMPLETED only with a fresh receipt; otherwise keep ACTIVE or BLOCKED.
- At review, remove stale backlog items and state the next constraint.
What it can do on your machine
Read from SKILL.md and the folder at commit 5a64514. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Project Flow Ops loads about 1.1k tokens when it runs. Until then it costs about 37 tokens; SKILL.md has 503 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Mark393295827/third-brain-v7-skills at commit 5a64514, republished under its MIT licence (© Mark393295827). 503 words, ~1,084 tokens.
Download SKILL.mdSave it as
.claude/skills/project-flow-ops/SKILL.md (or your agent's skills folder).- name
- project-flow-ops
- description
- Use when projects or tasks need explicit state, WIP control, ownership, definitions of done, blocker handling, and verified closure.
- metadata.version
- 8.1.0
- metadata.updated
- 2026-08-18
- metadata.profile
- stateful
- metadata.assumes
- Project state can be persisted and each active task can have one accountable owner.
- metadata.conflicts_with
- Hidden WIP, status by intuition, or marking work complete without a fresh verification receipt.
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.
Workflow
<intake>Normalize each item into {id, objective, owner, state, artifact, definition_of_done, budget, dependencies}. Reject duplicate ownership and distinguish waiting from active execution.
</intake><unknowns_gate>
If an active item lacks an owner, artifact, or observable definition of done, return NEEDS_INPUT. Probe the ambiguity with the largest impact on scheduling; do not guess priority from wording alone.
</unknowns_gate>
<execute>- Rank work by objective impact, urgency, dependency leverage, and cost of delay.
- Limit
ACTIVEto one or two items per owner. - Decompose the selected item until one bounded action can produce a reviewable artifact.
- For a blocker, record owner, missing condition, evidence, next probe, and review time; move independent work forward.
- Run the verification named in the definition of done.
- Move to
COMPLETEDonly with a fresh receipt; otherwise keepACTIVEorBLOCKED. - At review, remove stale backlog items and state the next constraint.
</execute><evaluate>Check state-transition legality, WIP limits, ownership, artifact existence, and completion evidence. Use an independent check for consequential deliverables. If verification fails, reopen the item with the failure evidence and smallest corrective action.
</evaluate><state_contract>
Persist {run_id, status, attempt, budget, evidence, unknowns, last_error, next_action} plus project objective, task ledger, dependency map, WIP count, transition history, and receipts. Transitions are append-only events; current state is derived from the latest valid event.
</state_contract>
Show full SKILL.md (180 more words)Show less
Failure Protocol
NEEDS_INPUT: ownership, priority boundary, or definition of done is missing.BLOCKED_DEPENDENCY: execution cannot continue; preserve the blocker contract and review time.VERIFY_FAILED: the artifact fails its named check; reopen rather than relabel completion.NO_PROGRESS: two reviews produce no new evidence; reduce scope, change strategy, or escalate.BUDGET_STOP: stop active work, persist state, and report the highest-value next action.
Output Contract
Return status, result (project board and transition decisions), evidence (artifacts and receipts), unknowns, and next_action with owner and review time.
Edge Cases
- Everything is marked urgent: use cost of delay and dependency leverage, then force one explicit tradeoff.
- A task is 90% complete but verification is unavailable: keep it active or blocked; never infer the final 10%.
Success Metrics
- Active WIP remains within the declared limit.
- Every completed task has an artifact and fresh verification receipt.
- Blocked work names an owner, next probe, and review time.
Quality Gates
- Every active task has one owner and bounded budget.
- State transitions are legal and traceable.
- Completion evidence is fresh and objective.
- The next constraint is explicit after each review.
</skill_contract>
© Mark393295827, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/project-flow-ops of Mark393295827/third-brain-v7-skills.
Open the folder on GitHubat commit 5a64514
Compare with similar skills
Project Flow Ops next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Project Flow Ops this skillMark393295827/third-brain-v7-skills | 141 | — | ~1.1k | Automated safety check: Pass | MIT | |
| Knowledge Opsaffaan-m/ECC | 275k | 2 repos | ~1.7k | Automated safety check: Pass | MIT | |
| Research Opsaffaan-m/ECC | 275k | 2 repos | ~902 | Automated safety check: Pass | MIT | |
| Terminal Opsaffaan-m/ECC | 275k | 2 repos | ~750 | Automated safety check: Pass | MIT | |
| Messages Opsaffaan-m/ECC | 275k | 1 repos | ~724 | Automated safety check: Pass | MIT | |
| Email Opsaffaan-m/ECC | 275k | 1 repos | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
Research Ops
affaan-m/ECC
Evidence-first current-state research workflow for ECC. An agent skill from affaan-m/ECC.
Terminal Ops
affaan-m/ECC
Evidence-first repo execution workflow for ECC. An agent skill from affaan-m/ECC.
Messages Ops
affaan-m/ECC
Evidence-first live messaging workflow for ECC. An agent skill from affaan-m/ECC.
Email Ops
affaan-m/ECC
Evidence-first mailbox triage, drafting, send verification, and sent-mail-safe follow-up workflow for ECC.
GitHub Ops
affaan-m/ECC
GitHub操作、自動化、APIインテグレーション、およびCI/CDワークフロー. An agent skill from affaan-m/ECC.
More from Mark393295827/third-brain-v7-skills
All 21 skills in this repoLoop Engineering
Mark393295827/third-brain-v7-skills
A skill your agent uses when a repeatable task must become a bounded Trigger - Execute - Verify - State loop, scheduled automation, goal agent, or metric-driven research cycle.
Graph Engineering
Mark393295827/third-brain-v7-skills
A skill your agent uses when a workflow has explicit data dependencies, independently executable branches, typed joins, or node-local recovery needs that justify a bounded static dependency graph.
Harness Engineering
Mark393295827/third-brain-v7-skills
A skill your agent uses when an agent workflow needs production-like runtime controls for context, tools, permissions, observability, scheduling, evaluation, recovery, or maintenance.
Agent Teams Command
Mark393295827/third-brain-v7-skills
A skill your agent uses when work has genuinely independent streams or distinct builder, evaluator, domain, and integration roles that require bounded multi-agent command scaled from 5 to 100+ agents.
AI Six Sigma Property Os
Mark393295827/third-brain-v7-skills
A skill your agent uses when property-service operations need an AI plus ontology plus DMAIC design for work orders, dispatch, quotes, evidence, CTQ metrics, and control dashboards.
Anthropic Os
Mark393295827/third-brain-v7-skills
A skill your agent uses when a personal or team operating system needs a bounded redesign using Four-C, closed-loop controls, 70/30 allocation, 3B creativity, experiments, and prediction-error…
Questions about Project Flow Ops
What does Project Flow Ops do?
A skill your agent uses when projects or tasks need explicit state, WIP control, ownership, definitions of done, blocker handling, and verified closure. Project Flow Ops is an agent skill from Mark393295827/third-brain-v7-skills. Use when projects or tasks need explicit state, WIP control, ownership, definitions of done, blocker handling, and verified closure.
When should I use Project Flow Ops?
Project Flow Ops fits situations like: tasks need explicit state; definitions of done; blocker handling; verified closure.
How do I install Project Flow Ops in Claude Code?
Run `npx skills add Mark393295827/third-brain-v7-skills --skill project-flow-ops -a claude-code`. Or copy the skill folder (skills/project-flow-ops in Mark393295827/third-brain-v7-skills) into .claude/skills/project-flow-ops in your project. Claude Code loads it when a task matches its description.
How do I install Project Flow Ops in Codex?
Run `npx skills add Mark393295827/third-brain-v7-skills --skill project-flow-ops -a codex`. Or copy the skill folder (skills/project-flow-ops in Mark393295827/third-brain-v7-skills) into .agents/skills/project-flow-ops in your project. Codex loads it when a task matches its description.
Can I use Project Flow Ops in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Mark393295827/third-brain-v7-skills --skill project-flow-ops -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/project-flow-ops, .gemini/skills/project-flow-ops, .github/skills/project-flow-ops and .opencode/skills/project-flow-ops in your project.
What does Project Flow Ops need to run?
SKILL.md names no scripts, command-line tools or credentials: Project Flow Ops is instructions for the agent only.
Does Project Flow Ops access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Project Flow Ops safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Project Flow Ops use?
Project Flow Ops is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Project Flow Ops use?
About 1.1k tokens (SKILL.md is roughly 4.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Project Flow Ops?
Skills that share tags, products or a category with Project Flow Ops: Knowledge Ops (affaan-m/ECC, 275k stars), Research Ops (affaan-m/ECC, 275k stars), Terminal Ops (affaan-m/ECC, 275k stars) and Messages Ops (affaan-m/ECC, 275k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Project Flow Ops?
Mark393295827 (a GitHub user) maintains it in Mark393295827/third-brain-v7-skills, which has 141 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on September 19, 2026.
Source: Mark393295827/third-brain-v7-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.