القائمة
Size a set of tickets — relative sizing against reference items the team has actually shipped, disagreement surfaced before numbers converge, epics detected and sent to be split.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
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.
استنادا إلى تصنيف SOC المهني
| name | estimation |
| description | Size a set of tickets — relative sizing against reference items the team has actually shipped, disagreement surfaced before numbers converge, epics detected and sent to be split. |
| disable-model-invocation | true |
Attach believable sizes to tickets. A size is a comparison, not a measurement — "like that auth ticket, roughly" beats "13 hours" every time, because the team has shipped the auth ticket and never shipped an hour.
Before sizing anything, pick 2–3 recently finished items the user remembers well — one small, one medium, one that hurt. These calibrate everything; without them every number is freestanding opinion.
Per ticket, in priority order: compare to the references, propose a size on the repo's scale (whatever docs/agents/board.md or existing issues use — points, T-shirt; adopt Fibonacci points if nothing exists yet). State the why of the comparison in one line — "touches the same three layers as [ref], but no migration" — then let the user agree or push back. Genuine disagreement is signal: it means the ticket hides an unshared assumption. Surface the assumption, don't average the numbers.
Anything that compares to nothing or lands past the scale's knee (≥13 points, XL) is an epic in disguise — route it to /refinement for splitting rather than blessing a giant number.
Write each agreed size onto the ticket (estimate field via the board skill, or a label). Done when every ticket in the requested set carries a size or a /refinement referral — none silently skipped — and the reference items used are named in one closing line, so the next session calibrates the same way.
