[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F5D1D4DTJTXT9PDJVTHYNT":3,"skill-same:01M7F5D1D4DTJTXT9PDJVTHYNT":49},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":28,"commitSha":29,"skillDirectory":30,"forksCount":31,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":34,"updatedAt":35,"install":36,"resources":48},"01M7F5D1D4DTJTXT9PDJVTHYNT","sprint-status",null,"Fast sprint status check. Reads the current sprint plan, scans story files for status, and produces a concise progress snapshot with burndown assessment and emerging risks. Run at any time during a sprint for quick situational awareness. Use when user asks 'how is the sprint going', 'sprint update', 'show sprint progress'.","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fsprint-status\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: sprint-status\ndescription: \"Fast sprint status check. Reads the current sprint plan, scans story files for status, and produces a concise progress snapshot with burndown assessment and emerging risks. Run at any time during a sprint for quick situational awareness. Use when user asks 'how is the sprint going', 'sprint update', 'show sprint progress'.\"\nargument-hint: \"[sprint-number or blank for current]\"\nuser-invocable: true\nallowed-tools: Read, Glob, Grep\nmodel: haiku\n---\n\n# Sprint Status\n\nThis is a fast situational awareness check, not a sprint review. It reads the\ncurrent sprint plan and story files, scans for status markers, and produces a\nconcise snapshot in under 30 lines. For detailed sprint management, use\n`\u002Fsprint-plan update` or `\u002Fmilestone-review`.\n\n**This skill is read-only.** It never proposes changes, never asks to write\nfiles, and makes at most one concrete recommendation.\n\n---\n\n## 1. Find the Sprint\n\n**Argument:** `$ARGUMENTS[0]` (blank = use current sprint)\n\n- If an argument is given (e.g., `\u002Fsprint-status 3`), search\n  `production\u002Fsprints\u002F` for a file matching `sprint-03.md`, `sprint-3.md`,\n  or similar. Report which file was found.\n- If no argument is given, find the most recently modified file in\n  `production\u002Fsprints\u002F` and treat it as the current sprint.\n- If `production\u002Fsprints\u002F` does not exist or is empty, report: \"No sprint\n  files found. Start a sprint with `\u002Fsprint-plan new`.\" Then stop.\n\nRead the sprint file in full. Extract:\n- Sprint number and goal\n- Start date and end date\n- All story or task entries with their priority (Must Have \u002F Should Have \u002F\n  Nice to Have), owner, and estimate\n\n---\n\n## 2. Calculate Days Remaining\n\nUsing today's date and the sprint end date from the sprint file, calculate:\n- Total sprint days (end minus start)\n- Days elapsed\n- Days remaining\n- Percentage of time consumed\n\nIf the sprint file does not include explicit dates, note \"Sprint dates not\nfound — burndown assessment skipped.\"\n\n---\n\n## 3. Scan Story Status\n\n**First: check for `production\u002Fsprint-status.yaml`.**\n\nIf it exists, read it directly — it is the authoritative source of truth.\nExtract status for each story from the `status` field. No markdown scanning needed.\nUse its `sprint`, `goal`, `start`, `end` fields instead of re-parsing the sprint plan.\n\n**If `sprint-status.yaml` does not exist** (legacy sprint or first-time setup),\nfall back to markdown scanning:\n\n1. If the entry references a story file path, check if the file exists.\n   Read the file and scan for status markers: DONE, COMPLETE, IN PROGRESS,\n   BLOCKED, NOT STARTED (case-insensitive).\n2. If the entry has no file path (inline task in the sprint plan), scan the\n   sprint plan itself for status markers next to that entry.\n3. If no status marker is found, classify as NOT STARTED.\n4. If a file is referenced but does not exist, classify as MISSING and note it.\n\nWhen using the fallback, add a note at the bottom of the output:\n\"⚠ No `sprint-status.yaml` found — status inferred from markdown. Run `\u002Fsprint-plan update` to generate one.\"\n\nOptionally (fast check only — do not do a deep scan): grep `src\u002F` for a\ndirectory or file name that matches the story's system slug to check for\nimplementation evidence. This is a hint only, not a definitive status.\n\n### Stale Story Detection\n\nAfter collecting status for all stories, check each IN PROGRESS story for staleness:\n\n- For each story that has a referenced file, read the file and look for a\n  `Last Updated:` field in the frontmatter or header (e.g., `Last Updated: 2026-04-01`\n  or `updated: 2026-04-01`). Accept any reasonable date field name: `Last Updated`,\n  `Updated`, `last-updated`, `updated_at`.\n- Calculate days since that date using today's date.\n- If the date is more than 2 days ago, flag the story as **STALE**.\n- If no date field is found in the story file, note \"no timestamp — cannot check staleness.\"\n- If the story has no referenced file (inline task), note \"inline task — cannot check staleness.\"\n\nSTALE stories are included in the output table and collected into an \"Attention Needed\"\nsection (see Phase 5 output format).\n\n**Stale story escalation**: If any IN PROGRESS story is flagged STALE, the burndown verdict\nis upgraded to at least **At Risk** — even if the completion percentage is within the normal\nOn Track window. Record this escalation reason: \"At Risk — [N] story(ies) with no progress in\n[N] days.\"\n\n---\n\n## 4. Burndown Assessment\n\nCalculate:\n- Tasks complete (DONE or COMPLETE)\n- Tasks in progress (IN PROGRESS)\n- Tasks blocked (BLOCKED)\n- Tasks not started (NOT STARTED or MISSING)\n- Completion percentage: (complete \u002F total) * 100\n\nAssess burndown by comparing completion percentage to time consumed percentage:\n\n- **On Track**: completion % is within 10 points of time consumed % or ahead\n- **At Risk**: completion % is 10-25 points behind time consumed %\n- **Behind**: completion % is more than 25 points behind time consumed %\n\nIf dates are unavailable, skip the burndown assessment and report \"On Track \u002F\nAt Risk \u002F Behind: unknown — sprint dates not found.\"\n\n---\n\n## 5. Output\n\nKeep the total output to 30 lines or fewer. Use this format:\n\n```markdown\n## Sprint [N] Status — [Today's Date]\n**Sprint Goal**: [from sprint plan]\n**Days Remaining**: [N] of [total] ([% time consumed])\n\n### Progress: [complete\u002Ftotal] tasks ([%])\n\n| Story \u002F Task         | Priority   | Status      | Owner   | Blocker        |\n|----------------------|------------|-------------|---------|----------------|\n| [title]              | Must Have  | DONE        | [owner] |                |\n| [title]              | Must Have  | IN PROGRESS | [owner] |                |\n| [title]              | Must Have  | BLOCKED     | [owner] | [brief reason] |\n| [title]              | Should Have| NOT STARTED | [owner] |                |\n\n### Attention Needed\n| Story \u002F Task         | Status      | Last Updated   | Days Stale | Note           |\n|----------------------|-------------|----------------|------------|----------------|\n| [title]              | IN PROGRESS | [date or N\u002FA]  | [N days]   | [STALE \u002F no timestamp — cannot check staleness \u002F inline task — cannot check staleness] |\n\n*(Omit this section entirely if no IN PROGRESS stories are stale or have timestamp concerns.)*\n\n### Burndown: [On Track \u002F At Risk \u002F Behind]\n[1-2 sentences. If behind: which Must Haves are at risk. If on track: confirm\nand note any Should Haves the team could pull.]\n\n### Must-Haves at Risk\n[List any Must Have stories that are BLOCKED or NOT STARTED with less than\n40% of sprint time remaining. If none, write \"None.\"]\n\n### Emerging Risks\n[Any risks visible from the story scan: missing files, cascading blockers,\nstories with no owner. If none, write \"None identified.\"]\n\n### Recommendation\n[One concrete action, or \"Sprint is on track — no action needed.\"]\n```\n\n---\n\n## 6. Fast Escalation Rules\n\nApply these rules before outputting, and place the flag at the TOP of the\noutput if triggered (above the status table):\n\n**Critical flag** — if Must Have stories are BLOCKED or NOT STARTED and\nless than 40% of the sprint time remains:\n\n```\nSPRINT AT RISK: [N] Must Have stories are not complete with [X]% of sprint\ntime remaining. Recommend replanning with `\u002Fsprint-plan update`.\n```\n\n**Completion flag** — if all Must Have stories are DONE:\n\n```\nAll Must Haves complete. Team can pull from Should Have backlog.\n```\n\n**Missing stories flag** — if any referenced story files do not exist:\n\n```\nNOTE: [N] story files referenced in the sprint plan are missing.\nRun `\u002Fstory-readiness sprint` to validate story file coverage.\n```\n\n---\n\n## Collaborative Protocol\n\nThis skill is read-only. It reports observed facts from files on disk.\n\n- It does not update the sprint plan\n- It does not change story status\n- It does not propose scope cuts (that is `\u002Fsprint-plan update`)\n- It makes at most one recommendation per run\n\nFor more detail on a specific story, the user can read the story file directly\nor run `\u002Fstory-readiness [path]`.\n\nFor sprint replanning, use `\u002Fsprint-plan update`.\nFor end-of-sprint retrospective, use `\u002Fmilestone-review`.\n","# Sprint Status\n\nThis is a fast situational awareness check, not a sprint review. It reads the\ncurrent sprint plan and story files, scans for status markers, and produces a\nconcise snapshot in under 30 lines. For detailed sprint management, use\n`\u002Fsprint-plan update` or `\u002Fmilestone-review`.\n\n**This skill is read-only.** It never proposes changes, never asks to write\nfiles, and makes at most one concrete recommendation.\n\n---\n\n## 1. Find the Sprint\n\n**Argument:** `$ARGUMENTS[0]` (blank = use current sprint)\n\n- If an argument is given (e.g., `\u002Fsprint-status 3`), search\n  `production\u002Fsprints\u002F` for a file matching `sprint-03.md`, `sprint-3.md`,\n  or similar. Report which file was found.\n- If no argument is given, find the most recently modified file in\n  `production\u002Fsprints\u002F` and treat it as the current sprint.\n- If `production\u002Fsprints\u002F` does not exist or is empty, report: \"No sprint\n  files found. Start a sprint with `\u002Fsprint-plan new`.\" Then stop.\n\nRead the sprint file in full. Extract:\n- Sprint number and goal\n- Start date and end date\n- All story or task entries with their priority (Must Have \u002F Should Have \u002F\n  Nice to Have), owner, and estimate\n\n---\n\n## 2. Calculate Days Remaining\n\nUsing today's date and the sprint end date from the sprint file, calculate:\n- Total sprint days (end minus start)\n- Days elapsed\n- Days remaining\n- Percentage of time consumed\n\nIf the sprint file does not include explicit dates, note \"Sprint dates not\nfound — burndown assessment skipped.\"\n\n---\n\n## 3. Scan Story Status\n\n**First: check for `production\u002Fsprint-status.yaml`.**\n\nIf it exists, read it directly — it is the authoritative source of truth.\nExtract status for each story from the `status` field. No markdown scanning needed.\nUse its `sprint`, `goal`, `start`, `end` fields instead of re-parsing the sprint plan.\n\n**If `sprint-status.yaml` does not exist** (legacy sprint or first-time setup),\nfall back to markdown scanning:\n\n1. If the entry references a story file path, check if the file exists.\n   Read the file and scan for status markers: DONE, COMPLETE, IN PROGRESS,\n   BLOCKED, NOT STARTED (case-insensitive).\n2. If the entry has no file path (inline task in the sprint plan), scan the\n   sprint plan itself for status markers next to that entry.\n3. If no status marker is found, classify as NOT STARTED.\n4. If a file is referenced but does not exist, classify as MISSING and note it.\n\nWhen using the fallback, add a note at the bottom of the output:\n\"⚠ No `sprint-status.yaml` found — status inferred from markdown. Run `\u002Fsprint-plan update` to generate one.\"\n\nOptionally (fast check only — do not do a deep scan): grep `src\u002F` for a\ndirectory or file name that matches the story's system slug to check for\nimplementation evidence. This is a hint only, not a definitive status.\n\n### Stale Story Detection\n\nAfter collecting status for all stories, check each IN PROGRESS story for staleness:\n\n- For each story that has a referenced file, read the file and look for a\n  `Last Updated:` field in the frontmatter or header (e.g., `Last Updated: 2026-04-01`\n  or `updated: 2026-04-01`). Accept any reasonable date field name: `Last Updated`,\n  `Updated`, `last-updated`, `updated_at`.\n- Calculate days since that date using today's date.\n- If the date is more than 2 days ago, flag the story as **STALE**.\n- If no date field is found in the story file, note \"no timestamp — cannot check staleness.\"\n- If the story has no referenced file (inline task), note \"inline task — cannot check staleness.\"\n\nSTALE stories are included in the output table and collected into an \"Attention Needed\"\nsection (see Phase 5 output format).\n\n**Stale story escalation**: If any IN PROGRESS story is flagged STALE, the burndown verdict\nis upgraded to at least **At Risk** — even if the completion percentage is within the normal\nOn Track window. Record this escalation reason: \"At Risk — [N] story(ies) with no progress in\n[N] days.\"\n\n---\n\n## 4. Burndown Assessment\n\nCalculate:\n- Tasks complete (DONE or COMPLETE)\n- Tasks in progress (IN PROGRESS)\n- Tasks blocked (BLOCKED)\n- Tasks not started (NOT STARTED or MISSING)\n- Completion percentage: (complete \u002F total) * 100\n\nAssess burndown by comparing completion percentage to time consumed percentage:\n\n- **On Track**: completion % is within 10 points of time consumed % or ahead\n- **At Risk**: completion % is 10-25 points behind time consumed %\n- **Behind**: completion % is more than 25 points behind time consumed %\n\nIf dates are unavailable, skip the burndown assessment and report \"On Track \u002F\nAt Risk \u002F Behind: unknown — sprint dates not found.\"\n\n---\n\n## 5. Output\n\nKeep the total output to 30 lines or fewer. Use this format:\n\n```markdown\n## Sprint [N] Status — [Today's Date]\n**Sprint Goal**: [from sprint plan]\n**Days Remaining**: [N] of [total] ([% time consumed])\n\n### Progress: [complete\u002Ftotal] tasks ([%])\n\n| Story \u002F Task         | Priority   | Status      | Owner   | Blocker        |\n|----------------------|------------|-------------|---------|----------------|\n| [title]              | Must Have  | DONE        | [owner] |                |\n| [title]              | Must Have  | IN PROGRESS | [owner] |                |\n| [title]              | Must Have  | BLOCKED     | [owner] | [brief reason] |\n| [title]              | Should Have| NOT STARTED | [owner] |                |\n\n### Attention Needed\n| Story \u002F Task         | Status      | Last Updated   | Days Stale | Note           |\n|----------------------|-------------|----------------|------------|----------------|\n| [title]              | IN PROGRESS | [date or N\u002FA]  | [N days]   | [STALE \u002F no timestamp — cannot check staleness \u002F inline task — cannot check staleness] |\n\n*(Omit this section entirely if no IN PROGRESS stories are stale or have timestamp concerns.)*\n\n### Burndown: [On Track \u002F At Risk \u002F Behind]\n[1-2 sentences. If behind: which Must Haves are at risk. If on track: confirm\nand note any Should Haves the team could pull.]\n\n### Must-Haves at Risk\n[List any Must Have stories that are BLOCKED or NOT STARTED with less than\n40% of sprint time remaining. If none, write \"None.\"]\n\n### Emerging Risks\n[Any risks visible from the story scan: missing files, cascading blockers,\nstories with no owner. If none, write \"None identified.\"]\n\n### Recommendation\n[One concrete action, or \"Sprint is on track — no action needed.\"]\n```\n\n---\n\n## 6. Fast Escalation Rules\n\nApply these rules before outputting, and place the flag at the TOP of the\noutput if triggered (above the status table):\n\n**Critical flag** — if Must Have stories are BLOCKED or NOT STARTED and\nless than 40% of the sprint time remains:\n\n```\nSPRINT AT RISK: [N] Must Have stories are not complete with [X]% of sprint\ntime remaining. Recommend replanning with `\u002Fsprint-plan update`.\n```\n\n**Completion flag** — if all Must Have stories are DONE:\n\n```\nAll Must Haves complete. Team can pull from Should Have backlog.\n```\n\n**Missing stories flag** — if any referenced story files do not exist:\n\n```\nNOTE: [N] story files referenced in the sprint plan are missing.\nRun `\u002Fstory-readiness sprint` to validate story file coverage.\n```\n\n---\n\n## Collaborative Protocol\n\nThis skill is read-only. It reports observed facts from files on disk.\n\n- It does not update the sprint plan\n- It does not change story status\n- It does not propose scope cuts (that is `\u002Fsprint-plan update`)\n- It makes at most one recommendation per run\n\nFor more detail on a specific story, the user can read the story file directly\nor run `\u002Fstory-readiness [path]`.\n\nFor sprint replanning, use `\u002Fsprint-plan update`.\nFor end-of-sprint retrospective, use `\u002Fmilestone-review`.\n",{"name":5,"model":24,"description":7,"allowed-tools":25,"argument-hint":26,"user-invocable":27},"haiku","Read, Glob, Grep","[sprint-number or blank for current]",true,"main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","05-技能与代理开发\u002Fsprint-status",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":27},[38,41,44],{"tool":39,"command":40},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill sprint-status",{"tool":42,"command":43},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill sprint-status",{"tool":45,"command":46},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill sprint-status","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fsprint-status\u002FSKILL.md",[],[50,57,62,69,76,83],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":19},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],{"skillNo":58,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]