القائمة
Operate execution flow — triage tasks, manage priorities, keep progress structured. Use when the user needs backlog control, task planning, or workflow coordination across projects.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | project-flow-ops |
| description | Operate execution flow — triage tasks, manage priorities, keep progress structured. Use when the user needs backlog control, task planning, or workflow coordination across projects. |
| version | 1.1 |
| updated | 2026-05-22 |
| assumes | There is a backlog or set of projects that can be ranked and reviewed. |
| conflicts_with | Do not replace behavior-design for habit formation or agent-teams-command for active multi-agent orchestration. |
Keep execution structured and progress visible — triage, plan, track, and review across projects.
Prompt
Use project-flow-ops to triage this backlog. Rank priorities, identify blockers, and produce the next execution plan.
Use Case
Expected Result
Output Example
Verification Case
Verified Effect
Scan current state:
ACTIVE: What's in progress now? (limit: 1-2)
BACKLOG: What's waiting? (ordered by priority)
BLOCKED: What's stuck and why?
COMPLETED: What's done since last review?
For each blocked item: identify the one thing that unblocks it.
Select the next task from the backlog with clear scope:
Task: [one-line description]
Why now: [urgency or opportunity]
Definition of done: [what "done" looks like]
Timebox: [max time to spend]
Rule: One task at a time. Context switching is the productivity killer.
During execution:
After completion:
| Priority | Criteria | Action |
|---|---|---|
| 🔴 Critical | Blocks others, deadline imminent | Do now |
| 🟡 Important | Moves key metric, this week | Schedule today |
| 🟢 Normal | Valuable, no deadline | Backlog |
| ⚪ Low | Nice-to-have | Someday/maybe |
Command V6 multi-agent work with bounded roles, ownership, worktree isolation, IPC, integration gates, cleanup, attention budgets, and verification loops. Use when the user needs Claude Code Agent Teams, parallel agents, delegation strategy, Ender-style commander training, von Neumann-style command architecture, Palantir-style ontology command boards, FDE field discovery, EDD integration gates, dynamic workflow tradeoffs, or multi-agent orchestration grounded in Obsidian wiki operating rules.
Multi-source deep research — search, synthesize, and deliver cited reports. Use when the user wants thorough research on any topic with evidence, citations, AI-era scientific-method boundaries, AutoResearch feasibility checks, source/claim ledgers, uncertainty handling, and STOW wiki handoff.
Design V6 runtime infrastructure around AI agents — permissions, tools, MCP/Skills/Hooks, feedback loops, observability, scheduled routines, von Neumann-style runtime architecture, and governance. Use when deploying agents to production, designing multi-agent systems, building agent harnesses, or turning Obsidian wiki rules into bounded runtime controls.
Turn a repeatable task into a bounded, evidence-driven agent loop. Use when Codex needs to decide whether a task merits a Goal, Loop, Automation, or AutoResearch pattern; define a loop contract; check trigger/state/tools/codebase readiness; choose single-agent versus maker-checker versus manager-workers topology; prevent runaway iteration; or repair a loop that stalls, self-grades, exceeds review budget, or writes without verified evidence.
Design or refactor agent skills, workflows, operating loops, and V6 knowledge-OS upgrades for model-native Agentic Engineering. Use when making skills more autonomous, concise, verifiable, long-horizon capable, token-efficient, lower-friction for human-LLM collaboration, or ready to promote Obsidian wiki learning into reusable agent behavior.
Execute a V6 daily knowledge compound closed loop — 7 Key Results from input to feedback with scoring, evidence, wiki write-back, and optional scheduled Obsidian daily-loop note. Use when the user wants to do a daily review, plan their day, run a knowledge workflow, or complete the generated daily knowledge-management loop.