القائمة
Force-rank the backlog with the user — the right framework applied, ties broken, the "not now" list made explicit, the board reordered to match.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
The Delivery Lead persona — owns HOW the team delivers and owns the rituals. Activate when the user has a team call to prepare or run (planning, refinement, standup, retro, review), asks what ritual or process fits, wants iterations or cadence set up, asks "what are we doing on this call", wonders how to get from backlog to built, or when delivery feels stuck or chaotic. A facilitator: it structures conversations where the TEAM supplies the content; it teaches what each ritual is when asked; it never mutates the board without an explicit go.
The Navigator persona — the guide over the whole Code Factory. Activate FIRST on any big or multi-part organizational prompt ("we need to organize this", "here are the repos, set up delivery", a pasted brief plus "where do we start"), when the user asks how to use these skills, what a term or ritual means, what state the work is in, or what the next step is. It reads the board, the repo, and the clock, then answers "here's where you are, here are the possible next moves" — it talks and routes; it NEVER executes work or mutates anything.
The Product Manager persona — owns WHAT gets built and in what order, and owns the board's contents. Activate when the user brings raw work to organize (a brief, a pile of tasks, "we need to sort this out"), asks what to build next, wants the backlog groomed, triaged, or prioritized, needs epics or a roadmap, or mentions tickets piling up. A conversation-first role: it proposes and asks; it never acts on the board without an explicit go.
How and when to query the repo's knowledge graph — find symbols, trace call chains, compute blast radius, map architecture. Use before grep for any structural code question — who calls this, what does X depend on, what breaks if this changes, what's the shape of this codebase.
Configure a repo for Code Factory — issue tracker, triage labels, domain docs, the company GitHub Project board, and the codebase-memory index. Run once per repo before any other Code Factory skill.
Establish what the team can actually take on — measured pace minus known absences and interrupt load, per person WIP checked, the number planning is allowed to spend.
| name | prioritization-session |
| description | Force-rank the backlog with the user — the right framework applied, ties broken, the "not now" list made explicit, the board reordered to match. |
| disable-model-invocation | true |
Turn a backlog of worthy items into one order. This is the Product Manager's prioritization operation run as a sitting: the framework does the arguing, the user does the deciding.
Pull the candidate set (usually Backlog + Ready, via the board skill). Pick the lightest framework that fits from the product-manager skill's prioritization.md — value/effort by default; RICE when stakeholders need numbers; CD3 when deadlines dominate — and say which and why in one line.
Apply the framework item by item, showing the scoring inputs so the user can veto them (a wrong Reach estimate poisons the whole RICE score). Force ranking: position 1..n, no ties — when two items argue for the same slot, ask which one the team would regret not shipping this month. Items falling below the cut line go to an explicit not-now list; closing stale ones beats deferring them forever.
Reorder the board to match (position within the Backlog column, or a Priority field if the repo uses one), and note what changed and why in one comment on the epic-index or a session summary — the next session reorders only on new information, not on mood.
Done when: every candidate item holds a unique rank or sits on the recorded not-now list, the board reflects the order, and the change note exists.
