Token导航 LogoToken导航

Agent Skill · 开发

blueprint-feature-tracker-status(蓝图功能跟踪器状态)

blueprint-feature-tracker-status 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

blueprint-feature-tracker-status 是开发类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描已通过,按安装量在开发类的 21,746 个 Skill 里排第 12,468。

总安装 1,272周安装 53GitHub Stars 28下载 424核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:blueprint-feature-tracker-status(蓝图功能跟踪器状态)
来源仓库:https://github.com/laurigates/claude-plugins
仓库路径:skills/blueprint-feature-tracker-status
安装命令:
npx skills add https://github.com/laurigates/claude-plugins --skill blueprint-feature-tracker-status
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/laurigates/claude-plugins --skill blueprint-feature-tracker-status

这个 Skill 是做什么的

开发类 Skill 面向写代码、改代码和排查问题,一般会读写仓库文件,部分还会执行构建或测试命令。

blueprint-feature-tracker-status 用于显示功能跟踪器的统计信息、阶段进度和完成摘要。适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。

读取 feature-tracker.json 文件,计算完成百分比并生成详细的进度报告。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

来源仓库内路径:skills/blueprint-feature-tracker-status

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/laurigates/claude-plugins --skill blueprint-fe…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

blueprint-feature-tracker-status 怎么安装?

在终端执行 npx skills add https://github.com/laurigates/claude-plugins --skill blueprint-feature-trac…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

blueprint-feature-tracker-status 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

blueprint-feature-tracker-status 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

blueprint-feature-tracker-status 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

blueprint-feature-tracker-status 用的人多吗?

公开数据是累计安装 1,272 次,近一周安装 53 次,下载 424 次,GitHub 28 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

blueprint-feature-tracker-status 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理开发类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

开发类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
skill-vetter

技能审查员 · OpenClaw

8,779,018986操作浏览器MIT-0通过
ontology

本体论 · OpenClaw

6,636,960576只读MIT-0通过
entra-app-registration

内部应用程序注册 · Codex、Claude

6,631,872764接触敏感数据未明确通过
entra-app-registration

内部应用程序注册 · Codex、Claude

3,757,680201接触敏感数据未明确通过
nano-banana-pro

纳米香蕉专业版 · OpenClaw

3,526,898364接触敏感数据MIT-0有提醒
blueprint-feature-tracker-status

蓝图功能跟踪器状态 · 本页

1,27228只读未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Display feature tracker statistics, phase progress, and completion summary.

Steps:

  1. Check if feature tracking is enabled:

- Look for docs/blueprint/feature-tracker.json - If not found, report: ` Feature tracking not enabled in this project. Run /blueprint:init and enable feature tracking to get started. `

  1. Load tracker data:

- Read feature-tracker.json - Extract project name, source document, last_updated - Get statistics section - Get phase information - Get PRD status

  1. Calculate derived metrics (if not in statistics):

- Count features by status at all nesting levels - Calculate completion percentage - Count features per phase - Count PRDs by status

  1. Display status report: Feature Tracker Status ====================== Project: {project} Source: {source_document} Last Updated: {last_updated} Overall Progress: ================== {progress_bar} {completion_percentage}% ({complete}/{total_features}) Complete: {complete} Partial: {partial} In Progress: {in_progress} Not Started: {not_started} Blocked: {blocked} Phase Progress: =============== {For each phase:} Phase {N}: {name} Status: {status} Features: {complete}/{total} complete PRD Coverage: ============= {For each PRD:} {PRD_NAME}: {status} Features: {features_implemented count} {If tests_passing:} Tests: {tests_passing} passing {If blocked features exist:} Blocked Features: ================= {For each blocked feature:} - {FR code}: {name} Reason: {implementation.notes or "No reason documented"} {If not_started features exist and count <= 10:} Ready to Start: =============== {List first 10 not_started features by phase order} - {FR code}: {name} (Phase {N}) {If any feature has non-empty implemented_by (monorepo portfolio, v3.3.0+):} Portfolio Features (linked to child workspaces): ================================================ {For each portfolio feature with implemented_by:} - {FR code}: {name} — derived status: {status} Implemented by: {For each link:} - {link.workspace}/{link.ref} → {status from child feature-tracker} {If top-level "workspaces" summary present:} Workspace Rollups: ================== {For each workspace key:} - {path}: {complete}/{total} ({completion_percentage}%) [last synced: {last_synced_at}]

4a. Resolve portfolio links (v3.3.0+): For each feature with non-empty implemented_by, open each referenced child <workspace>/docs/blueprint/feature-tracker.json and look up the ref FR to obtain its current status. Warn (do not fail) on missing workspaces or refs; suggest /blueprint:workspace-scan + /blueprint:feature-tracker-sync.

  1. Display visual progress bar: Create ASCII progress bar: [##########----------] 52.4%

- # for complete percentage - - for remaining - 20 characters wide

  1. Check for staleness:

- If last_updated is more than 7 days old, warn: ` Note: Tracker hasn't been synced in {N} days. Run /blueprint:feature-tracker-sync to update. `

  1. Prompt for next action (use AskUserQuestion): Build options dynamically based on state: question: "What would you like to do?" options: {Dynamic options based on state} - label: "Sync feature tracker" (if stale) description: "Update tracker from project state" - label: "Start next feature" (if not_started exist) description: "Begin work on the next pending feature" - label: "Continue current work" (if in_progress exist) description: "Resume work on in-progress features" - label: "View features by status" description: "List all features filtered by status" - label: "Exit" description: "Done viewing status" Based on selection:

- If stale → Include "Sync feature tracker" - If not_started features exist → Include "Start next feature" - If in_progress features exist → Include "Continue current work" - Always include "View detailed breakdown" and "Exit" - "Sync" → Run /blueprint:feature-tracker-sync - "Start next" → Show next not_started feature details, suggest starting - "Continue" → Show in_progress features, suggest continuing - "View by status" → Ask which status, then list matching features - "Exit" → End command

Example Output:

Feature Tracker Status
======================
Project: gooho
Source: REQUIREMENTS.md
Last Updated: 2026-01-01

Overall Progress:
==================
[##########----------] 52.4% (22/42)

Complete:     22
Partial:      4
In Progress:  2
Not Started:  14
Blocked:      0

Phase Progress:
===============
Phase 0: Foundation
Status: complete
Features: 4/4 complete

Phase 1: Core Gameplay
Status: complete
Features: 8/8 complete

Phase 2: Advanced Features
Status: in_progress
Features: 10/14 complete

Phase 3-8: Future Development
Status: not_started
Features: 0/16 complete

PRD Coverage:
=============
PRD_GAME_SETUP_FLOW: complete
  Features: 4
  Tests: 45 passing

PRD_TERRAIN_VISUAL_ENHANCEMENT: complete
  Features: 6
  Tests: 107 passing

PRD_ENTITY_BEHAVIOR_SYSTEM: complete
  Features: 8
  Tests: 187 passing

PRD_UI_CONTROLS_SYSTEM: partial
  Features: 3/5

Ready to Start:
===============
- FR3.1: Resource Types (Phase 3)
- FR3.2: Resource Gathering (Phase 3)
- FR3.3: Resource Storage (Phase 3)
- FR4.1: Basic Crafting (Phase 4)
- FR4.2: Recipe System (Phase 4)

Note: 14 features ready to start. Run `/blueprint:feature-tracker-sync` before beginning new work.

Quick Commands (shown at end):

Quick commands for feature tracker:
- jq '.statistics' docs/blueprint/feature-tracker.json
- jq '.. | objects | select(.status == "not_started") | .name' docs/blueprint/feature-tracker.json
- jq '.prds | to_entries | .[] | "\(.key): \(.value.status)"' docs/blueprint/feature-tracker.json

平台分布

Codex

36.95%
按下载量换算157

Claude

30.84%
按下载量换算131

Cursor

18.73%
按下载量换算79

Gemini CLI

9.92%
按下载量换算42

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills