القائمة
Build or update the roadmap — epics on a Now/Next/Later horizon on the board, dated only as far as honesty allows, with the narrative stakeholders can repeat.
التثبيت باستخدام 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 | roadmap |
| description | Build or update the roadmap — epics on a Now/Next/Later horizon on the board, dated only as far as honesty allows, with the narrative stakeholders can repeat. |
| disable-model-invocation | true |
Keep one roadmap: the board's roadmap view over epics. This ritual shapes it and keeps it honest — a roadmap that promises dates it can't know is a stakeholder incident scheduled in advance.
Via the board skill: active epics and their sub-issue progress, current iteration load, and delivery pace over the last 2–3 iterations (the only forecasting input that isn't opinion).
Place every epic in one of three bands — the band is the commitment level:
Anything more precise than the band allows gets pushed back into the epic body as a note. Check Now against measured pace: a Now band bigger than two iterations of measured delivery is a wish, not a plan — say so and force the cut with the Product Manager's priority order.
Three sentences a stakeholder can repeat: what's landing now, what's next and why that order, what we deliberately aren't doing. Put it in the roadmap view's description (or the epic-index issue).
Done when: every open epic sits in exactly one band, no Later item carries a date, target dates exist only in Now (and quarter-tags in Next), and the narrative matches what the bands actually say.
