[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72YVZHN4GVR5VYPATW9GV31":3,"skill-same:01M72YVZHN4GVR5VYPATW9GV31":45},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":13,"repositoryHtmlUrl":26,"repositoryHomepageUrl":6,"ownerHtmlUrl":27,"ownerBlogUrl":28,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M72YVZHN4GVR5VYPATW9GV31","agile-2-create-prd",null,"PRD in Confluence from Vision Doc. Triggers: write PRD, draft requirements. After skill 1, before skill 3.","cedricfarinazzo\u002Fagile-skills","cedricfarinazzo","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F34288081?v=4","01M72YSXQAMF9679DT1EGZV51E","01M72YSXRG377986J64G71PJZE",0,"MIT","https:\u002F\u002Fgithub.com\u002Fcedricfarinazzo\u002Fagile-skills\u002Fblob\u002Fmaster\u002Fagile-product\u002Fskills\u002Fagile-2-create-prd\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: agile-2-create-prd\ndescription: \"PRD in Confluence from Vision Doc. Triggers: write PRD, draft requirements. After skill 1, before skill 3.\"\n---\n\n# agile_2_create_prd\n\nSenior Product Manager translating a validated vision into a structured, actionable PRD: scan → extract from the Vision Doc → interview for the gaps → write the PRD → advise.\n\n## Confluence structure (canonical — identical across all agile-skills)\n\nEvery page is a child of the root folder created by `agile-1`. Read this tree before creating any page; never duplicate one that exists.\n\n```\n📁 [Project Name]                         (root — agile-1)\n├── 📄 Vision Doc — [Project]             (agile-1)\n├── 📄 PRD — [Project]                    (agile-2)\n├── 📄 Design Brief — [Project]           (agile-3 BRIEF)\n├── 📄 Specs UI — [Project]               (agile-3 INTEGRATE)\n├── 📄 ADR — [Project]                    (agile-4; current architecture state)\n├── 📄 Decision Log — [Project]           (agile-5; register, one row per decision)\n│   └── 📄 Decisions D001–D099 — [Project] (full entries by ID range: D100–D199, …)\n├── 📄 Working Agreements — [Project]     (agile-5 creates · agile-15 writes; rules in force: process, planning, operator, ops)\n├── 📄 Roadmap — [Project]                (agile-5 — INDEX only)\n│   ├── 📄 Parking Lot — [Project]        (agile-5; unscheduled and rejected ideas)\n│   ├── 📄 MVP — [Project]                (agile-5; an iteration page)\n│   │   └── 📄 Sprint 1 — [Project]       (agile-9 plans · agile-8 backlog · agile-15 closes)\n│   └── 📄 Iteration N — [Project]        (agile-5 ITERATION)\n│       └── 📄 Sprint N — [Project]\n├── 📁 Retrospectives — [Project]         (container: page or Confluence folder, agile-15; one Retro page per sprint)\n├── 📁 Closeouts — [Project]              (container: page or Confluence folder, agile-13; sibling of Retrospectives, never inside it)\n└── 📁 Extras — [Project]                 (folder; Debt Register (agile-15) + every page this tree does not name)\n```\n\n**Page placement.** Before creating a page, pick its parent from this tree and pass that parent's page id. Under the Roadmap sit only `Parking Lot`, `MVP` and `Iteration N`; under an `MVP` \u002F `Iteration N` page sit only its `Sprint N` pages. A closeout goes in `Closeouts`, a retro in `Retrospectives`, and any page the tree does not name (audit, coverage matrix, investigation, one-off report) in `Extras`. Reuse an existing folder whatever its exact title (`Extras` or `Extras — [Project]`); create it under the root only when absent. After creating, read the page back: a wrong `parentId` is fixed by moving the page (`mcp__atlassian__updateConfluencePage` with `parentId`), never by creating a second copy.\n\n**Page layouts.** Every page keeps the `##` headings below, in this order, and no others. A heading never carries a status, a date or a skill name, so a section is found by its name. Status lives in the page's `## Properties` (the Roadmap's `## Status` line); history lives in `## Change history` (`Date | Change | By`, one row per edit) and in the edit's version message, never in a status line, a heading or a table cell. Planning-time text is rewritten to the outcome when the sprint closes, not left beside it. agile-planning skills read the field-level templates from `agile-5-roadmap`; other skills use the headings and columns below.\n\n| Page | `##` headings, in order (table columns in brackets) |\n|---|---|\n| Roadmap | Status · Guiding principle · Iterations · Progress · Parking lot · Next step · Change history |\n| MVP \u002F Iteration N | Properties · Goal · Success criteria · Epics in scope · Sprints · Scope changes · Dependencies and risks · Feedback carried in · Research record · Closing summary · Change history |\n| Sprint N | Properties · Goal · Scope · Decisions · Backlog · Build order · Success criteria · Risks · Conclusion · Notes · Change history |\n| Decision Log | Register (ID · Alias · Date · By · Title · Status · Scope · Supersedes \u002F Amends · ADR § · Entry) · Change history |\n| Decisions D###–D### | one `## D### — \u003Ctitle>` per decision: Decision · Why · Alternatives rejected · Consequences · Supersedes \u002F Amends · Source |\n| Parking Lot | Ideas (Idea · Raised · Why parked · Earmark · Link) · Rejected (Idea · Date · By · Why) · Change history |\n| Working Agreements | Rules in force (Rule · Kind · Since · Source · Applies to) · Retired (Rule · Retired · Why) · Change history |\n| Debt Register | Open (Item · Source · Jira · Size · Target) · Closed (Item · Closed · How) · Change history |\n| Retrospectives \u002F Closeouts | Index (one row per report) when the container is a page; a Confluence folder has no body and lists its children itself |\n| Vision Doc · PRD · Design Brief · Specs UI · ADR | the template in the owning skill, ending with Change history |\n| Retro · Closeout | the template in the owning skill (written once) |\n\n**One fact, one home; every other page links to it.** Tickets, points and statuses → Jira. Verdicts and severity counts → the Closeout. Lessons → the Retro. Current architecture → the ADR. Decision text → the Decision Log; elsewhere only its ID and title. Sprint figures → the Sprint page's Properties, rolled up into its Iteration page's `## Sprints` and the Roadmap's `## Progress` **in the same run** that changes them. A dated snapshot that quotes a figure beside a link to its home (a Retro's velocity line, a verdict as the label of a Closeout link) is allowed; a second copy that someone maintains is not. Size budgets, counted on the rendered text (markup excluded): Roadmap ≤ 10k characters, MVP \u002F Iteration page ≤ 30k, Sprint page ≤ 50k.\n\n**A drifted page is fixed, not extended.** A page that breaks its layout — other headings, a changelog in a status line, one fact in several places, contradictory figures, over budget, a page under the wrong parent — is never patched in its old shape and never ignored. Write your own change in the layout, then plan the fix: list the drift and propose `agile-5-roadmap` RESTRUCTURE before finishing, and run it when the user agrees.\n\n## Step 1 — Scan existing state\n\nFind the project root folder, read the **Vision Doc in full**, check for an existing PRD child page, and search Jira for Epics already linked to the project (they may anticipate PRD decisions).\n\n- **A PRD exists** → read it section by section, report the status of each (\"complete \u002F placeholder \u002F missing\"), and resume from what is incomplete. Fill gaps and append; never overwrite.\n- **No Vision Doc** → stop: \"I can't find the Vision Doc for this project in Confluence. Please run skill 1 first, or point me to the right page.\"\n\n## Step 2 — Extract what the Vision Doc already answers\n\nMap it across before asking anything: problem statement → User Problem; target users → Personas; business objectives → Business Goals; success metrics → KPIs; constraints → Constraints; out of scope → Out of Scope. **Do not re-ask what the Vision Doc already states clearly.** Then identify what the PRD needs that it does not cover.\n\n## Step 3 — Interview for the PRD-specific gaps\n\n1. **User journeys** — the key flows as steps, not UI (\"user lands → authenticates → sees dashboard → exports report\").\n2. **Functional requirements** — capabilities, not implementation (\"users can filter by date range\", \"system sends email on completion\").\n3. **Non-functional requirements** — performance, availability, security, accessibility, compliance.\n4. **Dependencies** — other teams, systems, APIs, third parties.\n5. **Risks** — what could block or derail this.\n6. **Open questions** — what is still undecided and could move scope or design.\n\n**Ask** when a functional requirement is undefined enough that you cannot write even one bullet, when a \"journey\" is really just a label (\"users manage their account\"), when a dependency is hinted but unnamed (\"we'll need the auth system\" → \"which one, and does it already exist?\"), or when an obvious risk has gone unacknowledged. **Infer and flag** what the Vision Doc strongly implies (a B2C product implies mobile support) or where an industry default applies (\"assuming a 99.9% uptime target — correct me if your SLA differs\").\n\n**All questions in one message; every assumption stated in the same message. Never infer silently.** Lead with what you already have so the user only spends effort on the gaps:\n\n```\nI've read the Vision Doc. Already have: ✅ user problem · ✅ personas · ✅ business goals\n\nBefore I write the PRD:\n1. [missing user journey]  2. [undefined functional requirement]  3. [dependency or risk]\n\nI'm already assuming:\n- [Assumption] — correct me if wrong\n```\n\n## Step 4 — Write the PRD\n\nChild page of `[Project Name]`, titled `PRD — [Project Name]`:\n\n```\n# PRD — [Project Name]\n\n## Status\n[ ] Draft  [ ] In Review  [ ] Approved\nLast updated: [date] | Author: [PM name or \"AI-assisted\"] | Related: [Vision Doc]\n\n## 1. User Problem\nOne focused paragraph — who suffers, what the pain is, why it matters now. Refined from the Vision Doc, not rewritten from scratch.\n\n## 2. User Personas\nPer persona: role · goals · pain points · context of use.\n\n## 3. Business Goals\nEach with a measurable target.\n\n## 4. User Journeys\nPer flow, numbered user-action \u002F system-response steps. Intent level only — no UI or implementation detail.\n\n## 5. Functional Requirements\nGrouped by area (Authentication, Dashboard, Notifications…), numbered `FR-01`. \"Shall\" = mandatory, \"should\" = recommended.\n\n## 6. Non-Functional Requirements\nPerformance (e.g. page load \u003C 2s at p95) · Availability · Security · Accessibility (e.g. WCAG 2.1 AA) · Compliance.\n\n## 7. Out of Scope\n\n## 8. Dependencies\n| Dependency | Type (Internal\u002FExternal) | Team \u002F System | Status |\n\n## 9. Risks\n| Risk | Likelihood | Impact | Mitigation |\n\n## 10. KPIs & Success Metrics\n| Metric | Baseline | Target | Timeline |\n\n## 11. Open Questions\n| Question | Owner | Due date | Status |\n\n## Next Step\n→ Once approved, run skill 3: agile_3_design_brief\n\n## Change history\n| Date | Change | By |\n```\n\n## Step 5 — Resume logic\n\nRead the current PRD fully; per section, judge whether it holds real content or a placeholder, and fill only what is missing or marked TBD. Refresh `Last updated`. Never overwrite complete content — when a section changed materially since the last run (a newly discovered risk), update it and add a `## Change history` row saying what changed and why.\n\n## Step 6 — Advise\n\n```\n✅ Done:\n- PRD created\u002Fupdated under [Project Name]\n- Sections complete: [list]\n\n⚠️ Still needed (human action required):\n- Review and approve (set Status to \"Approved\")\n- Sections needing your input: [TBD list]\n- Open questions to resolve: [from section 11]\n\n👉 Next step — Skill 3: agile_3_design_brief (input: approved PRD)\n```\n\n## Principles\n\n- **Ask before writing** — never draft a section you have no real information for.\n- **No placeholder sections** — real content, or `TBD — [reason + owner]`.\n- **The PRD is the source of truth** — the ADR, Epics, and Stories all derive from it, so accuracy here saves rework everywhere downstream.\n","# agile_2_create_prd\n\nSenior Product Manager translating a validated vision into a structured, actionable PRD: scan → extract from the Vision Doc → interview for the gaps → write the PRD → advise.\n\n## Confluence structure (canonical — identical across all agile-skills)\n\nEvery page is a child of the root folder created by `agile-1`. Read this tree before creating any page; never duplicate one that exists.\n\n```\n📁 [Project Name]                         (root — agile-1)\n├── 📄 Vision Doc — [Project]             (agile-1)\n├── 📄 PRD — [Project]                    (agile-2)\n├── 📄 Design Brief — [Project]           (agile-3 BRIEF)\n├── 📄 Specs UI — [Project]               (agile-3 INTEGRATE)\n├── 📄 ADR — [Project]                    (agile-4; current architecture state)\n├── 📄 Decision Log — [Project]           (agile-5; register, one row per decision)\n│   └── 📄 Decisions D001–D099 — [Project] (full entries by ID range: D100–D199, …)\n├── 📄 Working Agreements — [Project]     (agile-5 creates · agile-15 writes; rules in force: process, planning, operator, ops)\n├── 📄 Roadmap — [Project]                (agile-5 — INDEX only)\n│   ├── 📄 Parking Lot — [Project]        (agile-5; unscheduled and rejected ideas)\n│   ├── 📄 MVP — [Project]                (agile-5; an iteration page)\n│   │   └── 📄 Sprint 1 — [Project]       (agile-9 plans · agile-8 backlog · agile-15 closes)\n│   └── 📄 Iteration N — [Project]        (agile-5 ITERATION)\n│       └── 📄 Sprint N — [Project]\n├── 📁 Retrospectives — [Project]         (container: page or Confluence folder, agile-15; one Retro page per sprint)\n├── 📁 Closeouts — [Project]              (container: page or Confluence folder, agile-13; sibling of Retrospectives, never inside it)\n└── 📁 Extras — [Project]                 (folder; Debt Register (agile-15) + every page this tree does not name)\n```\n\n**Page placement.** Before creating a page, pick its parent from this tree and pass that parent's page id. Under the Roadmap sit only `Parking Lot`, `MVP` and `Iteration N`; under an `MVP` \u002F `Iteration N` page sit only its `Sprint N` pages. A closeout goes in `Closeouts`, a retro in `Retrospectives`, and any page the tree does not name (audit, coverage matrix, investigation, one-off report) in `Extras`. Reuse an existing folder whatever its exact title (`Extras` or `Extras — [Project]`); create it under the root only when absent. After creating, read the page back: a wrong `parentId` is fixed by moving the page (`mcp__atlassian__updateConfluencePage` with `parentId`), never by creating a second copy.\n\n**Page layouts.** Every page keeps the `##` headings below, in this order, and no others. A heading never carries a status, a date or a skill name, so a section is found by its name. Status lives in the page's `## Properties` (the Roadmap's `## Status` line); history lives in `## Change history` (`Date | Change | By`, one row per edit) and in the edit's version message, never in a status line, a heading or a table cell. Planning-time text is rewritten to the outcome when the sprint closes, not left beside it. agile-planning skills read the field-level templates from `agile-5-roadmap`; other skills use the headings and columns below.\n\n| Page | `##` headings, in order (table columns in brackets) |\n|---|---|\n| Roadmap | Status · Guiding principle · Iterations · Progress · Parking lot · Next step · Change history |\n| MVP \u002F Iteration N | Properties · Goal · Success criteria · Epics in scope · Sprints · Scope changes · Dependencies and risks · Feedback carried in · Research record · Closing summary · Change history |\n| Sprint N | Properties · Goal · Scope · Decisions · Backlog · Build order · Success criteria · Risks · Conclusion · Notes · Change history |\n| Decision Log | Register (ID · Alias · Date · By · Title · Status · Scope · Supersedes \u002F Amends · ADR § · Entry) · Change history |\n| Decisions D###–D### | one `## D### — \u003Ctitle>` per decision: Decision · Why · Alternatives rejected · Consequences · Supersedes \u002F Amends · Source |\n| Parking Lot | Ideas (Idea · Raised · Why parked · Earmark · Link) · Rejected (Idea · Date · By · Why) · Change history |\n| Working Agreements | Rules in force (Rule · Kind · Since · Source · Applies to) · Retired (Rule · Retired · Why) · Change history |\n| Debt Register | Open (Item · Source · Jira · Size · Target) · Closed (Item · Closed · How) · Change history |\n| Retrospectives \u002F Closeouts | Index (one row per report) when the container is a page; a Confluence folder has no body and lists its children itself |\n| Vision Doc · PRD · Design Brief · Specs UI · ADR | the template in the owning skill, ending with Change history |\n| Retro · Closeout | the template in the owning skill (written once) |\n\n**One fact, one home; every other page links to it.** Tickets, points and statuses → Jira. Verdicts and severity counts → the Closeout. Lessons → the Retro. Current architecture → the ADR. Decision text → the Decision Log; elsewhere only its ID and title. Sprint figures → the Sprint page's Properties, rolled up into its Iteration page's `## Sprints` and the Roadmap's `## Progress` **in the same run** that changes them. A dated snapshot that quotes a figure beside a link to its home (a Retro's velocity line, a verdict as the label of a Closeout link) is allowed; a second copy that someone maintains is not. Size budgets, counted on the rendered text (markup excluded): Roadmap ≤ 10k characters, MVP \u002F Iteration page ≤ 30k, Sprint page ≤ 50k.\n\n**A drifted page is fixed, not extended.** A page that breaks its layout — other headings, a changelog in a status line, one fact in several places, contradictory figures, over budget, a page under the wrong parent — is never patched in its old shape and never ignored. Write your own change in the layout, then plan the fix: list the drift and propose `agile-5-roadmap` RESTRUCTURE before finishing, and run it when the user agrees.\n\n## Step 1 — Scan existing state\n\nFind the project root folder, read the **Vision Doc in full**, check for an existing PRD child page, and search Jira for Epics already linked to the project (they may anticipate PRD decisions).\n\n- **A PRD exists** → read it section by section, report the status of each (\"complete \u002F placeholder \u002F missing\"), and resume from what is incomplete. Fill gaps and append; never overwrite.\n- **No Vision Doc** → stop: \"I can't find the Vision Doc for this project in Confluence. Please run skill 1 first, or point me to the right page.\"\n\n## Step 2 — Extract what the Vision Doc already answers\n\nMap it across before asking anything: problem statement → User Problem; target users → Personas; business objectives → Business Goals; success metrics → KPIs; constraints → Constraints; out of scope → Out of Scope. **Do not re-ask what the Vision Doc already states clearly.** Then identify what the PRD needs that it does not cover.\n\n## Step 3 — Interview for the PRD-specific gaps\n\n1. **User journeys** — the key flows as steps, not UI (\"user lands → authenticates → sees dashboard → exports report\").\n2. **Functional requirements** — capabilities, not implementation (\"users can filter by date range\", \"system sends email on completion\").\n3. **Non-functional requirements** — performance, availability, security, accessibility, compliance.\n4. **Dependencies** — other teams, systems, APIs, third parties.\n5. **Risks** — what could block or derail this.\n6. **Open questions** — what is still undecided and could move scope or design.\n\n**Ask** when a functional requirement is undefined enough that you cannot write even one bullet, when a \"journey\" is really just a label (\"users manage their account\"), when a dependency is hinted but unnamed (\"we'll need the auth system\" → \"which one, and does it already exist?\"), or when an obvious risk has gone unacknowledged. **Infer and flag** what the Vision Doc strongly implies (a B2C product implies mobile support) or where an industry default applies (\"assuming a 99.9% uptime target — correct me if your SLA differs\").\n\n**All questions in one message; every assumption stated in the same message. Never infer silently.** Lead with what you already have so the user only spends effort on the gaps:\n\n```\nI've read the Vision Doc. Already have: ✅ user problem · ✅ personas · ✅ business goals\n\nBefore I write the PRD:\n1. [missing user journey]  2. [undefined functional requirement]  3. [dependency or risk]\n\nI'm already assuming:\n- [Assumption] — correct me if wrong\n```\n\n## Step 4 — Write the PRD\n\nChild page of `[Project Name]`, titled `PRD — [Project Name]`:\n\n```\n# PRD — [Project Name]\n\n## Status\n[ ] Draft  [ ] In Review  [ ] Approved\nLast updated: [date] | Author: [PM name or \"AI-assisted\"] | Related: [Vision Doc]\n\n## 1. User Problem\nOne focused paragraph — who suffers, what the pain is, why it matters now. Refined from the Vision Doc, not rewritten from scratch.\n\n## 2. User Personas\nPer persona: role · goals · pain points · context of use.\n\n## 3. Business Goals\nEach with a measurable target.\n\n## 4. User Journeys\nPer flow, numbered user-action \u002F system-response steps. Intent level only — no UI or implementation detail.\n\n## 5. Functional Requirements\nGrouped by area (Authentication, Dashboard, Notifications…), numbered `FR-01`. \"Shall\" = mandatory, \"should\" = recommended.\n\n## 6. Non-Functional Requirements\nPerformance (e.g. page load \u003C 2s at p95) · Availability · Security · Accessibility (e.g. WCAG 2.1 AA) · Compliance.\n\n## 7. Out of Scope\n\n## 8. Dependencies\n| Dependency | Type (Internal\u002FExternal) | Team \u002F System | Status |\n\n## 9. Risks\n| Risk | Likelihood | Impact | Mitigation |\n\n## 10. KPIs & Success Metrics\n| Metric | Baseline | Target | Timeline |\n\n## 11. Open Questions\n| Question | Owner | Due date | Status |\n\n## Next Step\n→ Once approved, run skill 3: agile_3_design_brief\n\n## Change history\n| Date | Change | By |\n```\n\n## Step 5 — Resume logic\n\nRead the current PRD fully; per section, judge whether it holds real content or a placeholder, and fill only what is missing or marked TBD. Refresh `Last updated`. Never overwrite complete content — when a section changed materially since the last run (a newly discovered risk), update it and add a `## Change history` row saying what changed and why.\n\n## Step 6 — Advise\n\n```\n✅ Done:\n- PRD created\u002Fupdated under [Project Name]\n- Sections complete: [list]\n\n⚠️ Still needed (human action required):\n- Review and approve (set Status to \"Approved\")\n- Sections needing your input: [TBD list]\n- Open questions to resolve: [from section 11]\n\n👉 Next step — Skill 3: agile_3_design_brief (input: approved PRD)\n```\n\n## Principles\n\n- **Ask before writing** — never draft a section you have no real information for.\n- **No placeholder sections** — real content, or `TBD — [reason + owner]`.\n- **The PRD is the source of truth** — the ADR, Epics, and Stories all derive from it, so accuracy here saves rework everywhere downstream.\n",{"name":5,"description":7},"master","5f163e1c0720bcc8f5c9caf4e675c301585b3b29","agile-product\u002Fskills\u002Fagile-2-create-prd","https:\u002F\u002Fgithub.com\u002Fcedricfarinazzo\u002Fagile-skills","https:\u002F\u002Fgithub.com\u002Fcedricfarinazzo","https:\u002F\u002Fcedricfarinazzo.fr\u002F","IT engineer specialized in Cybersecurity and SRE\u002FDevOps","2026-11-13 03:28:11",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add cedricfarinazzo\u002Fagile-skills --skill agile-2-create-prd",{"tool":37,"command":38},"bunx","bunx skills add cedricfarinazzo\u002Fagile-skills --skill agile-2-create-prd",{"tool":40,"command":41},"pnpm","pnpm dlx skills add cedricfarinazzo\u002Fagile-skills --skill agile-2-create-prd","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fcedricfarinazzo\u002Fagile-skills\u002Fblob\u002Fmaster\u002Fagile-product\u002Fskills\u002Fagile-2-create-prd\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":18},"01M72YXMSVD28QYHJ70AVJ9SBP","session-audit","Audit the cost and efficiency of Claude Code sessions that ran agile-skills: per-skill and per-subagent spend, a before\u002Fafter delta normalised by work shipped, and ranked skill improvements. Triggers: audit this session's cost, analyze the session transcripts, compare before and after sessions, is the new version more efficient, where do the tokens go, subagent cost breakdown, find efficiency improvements.","https:\u002F\u002Fgithub.com\u002Fcedricfarinazzo\u002Fagile-skills\u002Fblob\u002Fmaster\u002Fsession-audit\u002Fskills\u002Fsession-audit\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":18},"01M72YXG2E8CAD3YHTHFESKF2B","deep-it-project-review","Autonomously perform a deep, evidence-backed technical review of a software or IT project across applicable architecture, code, security, delivery, operations, and lifecycle domains without modifying project files. Triggers: deep IT project review, technical project review, architecture audit, repository assessment, assess this codebase, review this project.","https:\u002F\u002Fgithub.com\u002Fcedricfarinazzo\u002Fagile-skills\u002Fblob\u002Fmaster\u002Fproject-review\u002Fskills\u002Fdeep-it-project-review\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"01M72YXBQJCSDC60PVKA6H9SJ3","test-refactor","Audit one test suite at a time for dead weight, duplication, parallel-unsafety and runtime cost, or characterize behavior before a risky refactor — with production code frozen and good coverage kept, proven per module rather than assumed. Triggers: test refactor, characterize before refactor, characterization tests, clean the tests, refactor the tests, test suite audit, DRY the tests, parallelize the test suite, speed up the tests.","https:\u002F\u002Fgithub.com\u002Fcedricfarinazzo\u002Fagile-skills\u002Fblob\u002Fmaster\u002Fdeep-refactor\u002Fskills\u002Ftest-refactor\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":18},"01M72YX7QCP7MA1H2DSWVG6Y4C","doc-refactor","Audit every markdown file in a repo — READMEs, docs\u002F, and agent-instruction files — for lies, drift, duplication and bloat, then ticket and ship the cleanup as a sequenced PR train, with source code frozen and every surviving claim verified against the repo rather than read. Triggers: doc refactor, refactor the docs, clean the docs, documentation audit, README audit, docs are stale, DRY the docs, audit every markdown file.","https:\u002F\u002Fgithub.com\u002Fcedricfarinazzo\u002Fagile-skills\u002Fblob\u002Fmaster\u002Fdeep-refactor\u002Fskills\u002Fdoc-refactor\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"01M72YX36Z9MSECJH7FJ4JM09Z","deep-refactor","Audit an entire codebase for defects, waste and debt, then ticket and ship the findings as a sequenced PR train — without breaking the test contract. Triggers: deep refactor, refactor audit, clean the codebase, DRY pass, audit and fix everything.","https:\u002F\u002Fgithub.com\u002Fcedricfarinazzo\u002Fagile-skills\u002Fblob\u002Fmaster\u002Fdeep-refactor\u002Fskills\u002Fdeep-refactor\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"01M72YWZ1HEXSKQ7JCSVR2HPT0","agile-sprint-drain","Drain the active sprint to a fixed point: auto-alternate agile-10-implement (build) and agile-11-merge-train (merge) until both empty (DRAINED) or blocked (STUCK). Optional concurrency=N, dispatch=session, max-merges=N. Triggers: drain the sprint, run the sprint to completion, implement and merge until done, clear the whole board, ship the sprint.","https:\u002F\u002Fgithub.com\u002Fcedricfarinazzo\u002Fagile-skills\u002Fblob\u002Fmaster\u002Fagile-sprint-drain\u002Fskills\u002Fagile-sprint-drain\u002FSKILL.md",[],[]]