AGENT SKILL

inspire-task

Task tracker: create / update / close / list / show tickets in inspire_kb/99_tracker/. A plain-file kanban (one Markdown file per ticket, no external tool) for tracking work, drift, and skill-feedback. Use to open, advance, close, or query tickets.

License 许可
MIT
所属仓库
Genomcore/inspire
最近更新
2026-11-13
Stars
★ 0
Forks
1

01 前言 Front Matter

name
inspire-task
description
Task tracker: create / update / close / list / show tickets in inspire_kb/99_tracker/. A plain-file kanban (one Markdown file per ticket, no external tool) for tracking work, drift, and skill-feedback. Use to open, advance, close, or query tickets.

02 资源文件 1

03 SKILL.md 正文

/inspire-task — Task tracker

Scope

A plain-file ticket tracker under inspire_kb/99_tracker: one Markdown file per ticket, the only source of truth — no external tool, no generated cache. Open tickets live at tickets/*.md; closed ones are archived under tickets/archive/*.md so default scans see only active work.

The on-disk contract — storage layout, frontmatter schema, enums, ID scheme — lives in references/tracker-format.md. Read it before any subcommand that writes (create, update, close).

Invocation

  • /inspire-task create {title} [--epic X --size M --importance Mid --skills a,b]
  • /inspire-task update TASK-{id} [--field value ...]
  • /inspire-task close TASK-{id} [--cancelled --reason "..."]
  • /inspire-task list [--status X --epic Y --skill prototype] (read-only)
  • /inspire-task show TASK-{id} (read-only)

Subcommand: create {title} [--flags]

  1. Resolve @handle from git config user.email (cached per session).
  2. Resolve today's date from CLAUDE.md currentDate or date +%Y-%m-%d.
  3. Generate a random 6-char base36 ID; verify the file doesn't exist; regenerate if it does.
  4. Apply flags --epic (required), --size (default M), --importance (default Mid), --skills (comma-separated, default empty), --status (default Open), --blocked-by, --related-to.
  5. Write the file with frontmatter + an empty ## Description body (or --body).
  6. Print the new ID to stdout.

Subcommand: update TASK-{id} [--flags]

  1. Resolve the ticket path (tickets/ then tickets/archive/). Error if neither.
  2. Apply flag changes (validate against the enums in the format reference).
  3. Set updated to today.
  4. Status transitions move the file:
    • New status ∈ {Done, Cancelled} and file in tickets/ → write to tickets/archive/ and remove the original; fill closed_by / closed_at.
    • Back to Open from tickets/archive/ → write to tickets/; clear closed_by / closed_at.
    • Otherwise, write in place.
  5. Show a diff before saving.

Subcommand: close TASK-{id} [--cancelled --reason "..."]

Shortcut that transitions an open ticket to a closed status and archives it: default status: Done; with --cancelled, status: Cancelled (append a ## Cancellation reason if --reason given). Sets closed_by / closed_at / updated, and moves the file to tickets/archive/.

Subcommand: list [--filter]

  1. Scan inspire_kb/99_tracker/tickets/*.md (top-level, non-recursive — excludes archive/). Parse frontmatter.
  2. With --include-archived (or --all), also scan tickets/archive/*.md.
  3. Filters: --status, --epic, --size, --importance, --reporter, --skill (matches if skills contains the value), --blocked.
  4. Print a compact table to stdout: id | status | epic | size | importance | skills | title.
  5. Read-only.

Subcommand: show TASK-{id}

Read the file (tickets/ then tickets/archive/) and print frontmatter + body. Read-only.

Skill-feedback tickets (convention)

When a skill's usage produces a friction signal worth capturing — operator pushback, a recurring AskUserQuestion that should default, drift from what the skill anticipated — file a standard ticket:

epic: skill-feedback
skills: [<source-skill>]
size: S
importance: Low

Title format: {skill-name}: <short friction observation>. Body: ## Observation · ## Where it surfaced · ## Suggested follow-up. It reuses standard ticket infrastructure — no new tooling; the operator decides when an observation deserves a ticket, and skills surface candidates conversationally.

A ticket captures local, actionable friction. The ticket-vs-lesson routing and the offer protocol live in _references/lesson-capture.md; the rule for a confirmed ticket graduating into a lesson lives in inspire-lesson/SKILL.md § Relationship to the tracker.

Rules

Output language. Write ticket prose in the project's declared output_language (default English), per _references/output-language.md. Machine-read tokens (frontmatter keys/values, enum values, TASK- IDs, filenames) stay verbatim.

Writing contract. Ticket prose follows _references/writing-style.md.

Lesson capture. At a natural pause, when the operator's feedback should change how this skill behaves, offer /inspire-lesson note — never auto-write a lesson. Protocol and ticket-vs-lesson routing: _references/lesson-capture.md.

  1. One file per ticket. Filename = TASK-{id}.md; the id field matches.
  2. IDs never reused. Don't delete files — archive them.
  3. Open vs archived location is derived from status. Keep the location consistent with status on every transition.
  4. updated is auto-managed. Don't edit it by hand.
  5. closed_by / closed_at only when status ∈ {Done, Cancelled}.
  6. Body markdown is free. Description / Acceptance criteria / Notes suggested.
  7. Concurrent edits are safe — random IDs, no locking.

Related skills

  • Every skill consults the tracker (list) at the start of multi-step work and files a skill-feedback ticket when a session surfaces friction.
  • /inspire-workspace structure validates the tracker's on-disk invariants (location ↔ status, ID format, no duplicates).

04 同仓库更多 Skills

Genomcore
Genomcore/inspire

update

Update this project's INSPIRE runtime to the installed plugin's version: report drift, re-materialize unchanged files, and refuse to clobber local edits. Use after /plugin update inspire reports a newer base.

★ 0
Genomcore
Genomcore/inspire

migrate

Move this project's knowledge base from the layered layout (01_adr, 02_modules, 03_features, 04_domain, 05_screens and the surface roster) to the concept layout under inspire_kb/01_spec/, where every artifact has a typed extension, and convert its [[wikilinks]] to relative Markdown links. Run once, on purpose, after /inspire:update reports the layered layout or counts wikilinks. Rebuilds nothing that is already built.

★ 0
Genomcore
Genomcore/inspire

init

Install the INSPIRE runtime into this repository: materialize the skills, validators, hooks and knowledge-base skeleton, register the hooks, and freeze the runtime version. Run once per project. Use when setting up INSPIRE in a new or existing repo.

★ 0
Genomcore
Genomcore/inspire

inspire-workspace

Workspace-level validation: the global pre-PR review (orchestrating module + cross-module checks) and vault-structure validation. Use for the required pre-merge gate and top-level structure checks. ADR lifecycle lives in /inspire-adr; the task tracker in /inspire-task.

★ 0
Genomcore
Genomcore/inspire

inspire-spike

Vertical spikes: register and harvest external functional-prototype repos. A spike is a narrow, deep, throwaway build in its OWN repo that answers 'can we build it as we think?'. Use to register such a repo (name/reference it, set up its learnings hygiene) and to capture its learnings into the vault as a gap analysis against the current project.

★ 0
Genomcore
Genomcore/inspire

inspire-screens

Create and validate screens (a screen is the UI spec for one view). A screen declares its own bindings — data sources, dispatches, navigation, states — and names a shared layout and shared components as dependencies. Use when designing or reviewing an application's screens.

★ 0