“tracker”的搜索结果

Track changes and versions in AI systems. TRIGGERS - Use when user needs help with ai-changelog-tracker related tasks.

中文简介正在准备中。当前显示原文说明。

Design AR tracking with aging and collection processes. TRIGGERS - Use when user needs help with accounts-receivable-tracker related tasks.

中文简介正在准备中。当前显示原文说明。

Design AP tracking with payment scheduling. TRIGGERS - Use when user needs help with accounts-payable-tracker related tasks.

中文简介正在准备中。当前显示原文说明。

Sets up an `## Agent skills` block in AGENTS.md/CLAUDE.md and `docs/agents/` so the engineering skills know this repo's issue tracker (GitHub or local markdown), triage label vocabulary, and domain doc layout. Run before first use of `to-issues`, `to-prd`, `triage`, `diagnose`, `tdd`, `improve-codebase-architecture`, or `zoom-out` — or if those skills appear to be missing context about the issue tracker, triage labels, or domain docs.

中文简介正在准备中。当前显示原文说明。

Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker).

中文简介正在准备中。当前显示原文说明。

Create a bilingual Notion job application tracker and organize job links, full JDs, screenshots, and application updates into it. Use for bulk job tracking, exhaustive employer-requirement extraction, and CPT/OPT/sponsorship recording.

中文简介正在准备中。当前显示原文说明。

Use when the user asks to track, scan, monitor, digest, or maintain a reading queue for new papers from top journals, Nature/Science/Cell/PNAS families, or any research field. Works with any discipline — ecology, environment, CS, medicine, physics, social sciences, etc.

中文简介正在准备中。当前显示原文说明。

Triage the Gaia issue backlog and skill-batch intake queue. Use this skill when someone asks to: "triage issues", "clean up the issue tracker", "review the backlog", "close stale issues", "process the intake queue", "review skill-batches", "evaluate draft skill proposals", "approve or reject pending skills", "is this issue still valid?", "what's clogging the backlog?", "run a triage pass", or /gaia-triage. Covers two workstreams: (1) GitHub issue lifecycle — identifying resolved, stale, or need-more-info issues and acting on them via gh CLI; (2) skill-batch intake — evaluating draft proposals in registry-for-review/skill-batches/ and routing them toward promotion or rejection. This is the gatekeeping step before new skills enter the canonical registry; and (3) a cross-repo triage sweep — sizing, P0-P4 prioritization, umbrella/epic synthesis, and assignment across every gaia-research org repo, on the one headquarters tracker.

中文简介正在准备中。当前显示原文说明。

Chart a too-big effort as a shared map of decision tickets on the Gaia headquarters issue tracker, then resolve them one at a time until the way to the destination is clear. Use when someone says: "this is too big for one session", "chart a map", "wayfinder map", "plan this effort", "what do we need to decide first", "open a wayfinder", "work the map", "what's on the frontier", or /wayfinder. Covers any gaia-research org repo — gaia-skill-tree, gaia-research, gaia-skill-heaven and beyond — but every map and every ticket lives on ONE tracker: gaia-research/gaia-skill-tree. This is cartography (planning an effort as decisions), NOT triage of an existing backlog — for that use /gaia-triage.

中文简介正在准备中。当前显示原文说明。

Generate weekly or monthly status updates from local PM data. Use this skill when: - It's end of week and you need a status update for leadership or stakeholders - You need a monthly executive summary - You want to draft an email update using data from meetings, tracker tickets, and decisions - The user says "weekly update", "status report", "what happened this week?", "weekly summary" - The user says "Friday update", "send status email", "EOW update" Pulls from work logs, meetings, ticket tracker, and decisions — no manual input needed.

中文简介正在准备中。当前显示原文说明。

Sets up an `## Agent skills` block in AGENTS.md/CLAUDE.md and `docs/agents/` so the engineering skills know this repo's issue tracker (GitHub or local markdown), triage label vocabulary, and domain doc layout. Run before first use of `to-issues`, `to-prd`, `triage`, `diagnose`, `tdd`, `improve-codebase-architecture`, or `zoom-out` — or if those skills appear to be missing context about the issue tracker, triage labels, or domain docs.

中文简介正在准备中。当前显示原文说明。

Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker — edges as text in one file per ticket locally, or native blocking links on a real tracker.

中文简介正在准备中。当前显示原文说明。

Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker — edges as text in one file per ticket locally, or native blocking links on a real tracker.

中文简介正在准备中。当前显示原文说明。

feature ready と task ready を分離したいとき、依存・tracker parity・resource scope・active lease を満たす conflict-free batch を算出したいときに使う。

中文简介正在准备中。当前显示原文说明。

tracker_binding に従い dev-graph と Beads を同期したいとき、GitHub Issues/Projects/PR lifecycle を冪等収束したいときに使う。

中文简介正在准备中。当前显示原文说明。

Drafts one weekly status update or team status email (done, in progress, blocked, next, asks) from the notes, task lists, tracker exports and messages the user attaches, pastes or makes reachable, every bullet traced to a source and every gap marked UNKNOWN, returned in the chat as Markdown for the user to review and send. Use when the user asks to "write my weekly status update", "draft the team status email", "turn my notes into a status report", "what did we get done this week", "summarise this week for my manager" or "prepare Friday's update". Do not use for maintaining a project's living logs or a project-level report built from them, use project-status-tracker instead. Drafts for human review; never approves, authorises or signs off.

中文简介正在准备中。当前显示原文说明。

Use when the user asks to "measure how our narrative is landing", "track echo rate against our canon lexicon", or "check how AI answer engines describe our brand"; produces a resonance report — echo rate (overlap of market language with the narrative-registry canon lexicon, method declared), AI-answer perception via tavily.py --answer (proxy-labeled), share-of-voice on a locked competitor panel (reusing share-of-voice-tracker), and resonance signals from bluesky.py / gdelt.py / pageviews.py — every number labeled Measured / proxy / User-provided, feeding the TALE E dimension and the upstream of the E1 evidence-integrity veto. Not for rebuilding share-of-voice machinery — use share-of-voice-tracker; not for own-site GA4/GSC analytics — use performance-monitor; not for scoring TALE profile result — use narrative-quality-auditor; not for adjudicating claims — use offer-claims-registry. 回声率/AI回答感知/份额之声/共鸣信号

中文简介正在准备中。当前显示原文说明。

Build one spreadsheet for an event covering guests, vendors, timeline and budget, from your event brief and vendor list, and draft the vendor messages for your GO. Use for "event tracker", "plan this event", "track vendors and budget", "event spreadsheet".

中文简介正在准备中。当前显示原文说明。

Build experiment tracking systems for AI. TRIGGERS - Use when user needs help with ai-experiment-tracker related tasks.

中文简介正在准备中。当前显示原文说明。

Track changes and versions in AI systems. TRIGGERS - Use when user needs help with ai-changelog-tracker related tasks.

中文简介正在准备中。当前显示原文说明。

Design AP tracking with payment scheduling. TRIGGERS - Use when user needs help with accounts-payable-tracker related tasks.

中文简介正在准备中。当前显示原文说明。

Design AR tracking with aging and collection processes. TRIGGERS - Use when user needs help with accounts-receivable-tracker related tasks.

中文简介正在准备中。当前显示原文说明。

Sets up an `## Agent skills` block in AGENTS.md/CLAUDE.md and `docs/agents/` so the engineering skills know this repo's issue tracker (GitHub or local markdown), triage label vocabulary, and domain doc layout. Run before first use of `to-issues`, `to-prd`, `triage`, `diagnose`, `tdd`, `improve-codebase-architecture`, or `zoom-out` — or if those skills appear to be missing context about the issue tracker, triage labels, or domain docs.

中文简介正在准备中。当前显示原文说明。

读取规格说明和相关工单的依赖关系，安排多个代理推进实现。经过测试、代码审查和问题修正后，将成果汇总到一个集成分支，并完成工单处理。

• 实现分散在多个工单中的需求
• 并行实现相互独立的任务
• 将成果汇总到集成分支