- Skills
- 58
- 仓库
- 1
- 职业覆盖
- 0
- 场景覆盖
- 0
- Stars
- ★ 0
TurboKast 的 Skills 58
mythhelm-deliver-backlog
Coordinate a MYTHHELM backlog run with the shared stage checks and maintainer checkpoints.
mythhelm-bootstrap
Orient a Grok Build session in the MYTHHELM repository before task or spec work.
vendor-consult
Run one advisory stage consult (premise-ground, spec-validate, task-review, change-review, stuck-oracle, dossier) with an optional external vendor, then adjudicate the answer at its anchors
update-docs
Bring README, docs/, knowledge/, WORKFLOW.md and CLAUDE.md in line with what a shipped spec or a merged change actually did — find every statement the change made stale, fix it where readers look, and add only the new facts they need
triage
Score an idea or a GitHub issue against the master spec's stages, gates and commitments, check it for duplicates, and recommend whether it becomes a backlog card; read-only
test-driven-development
Red-green-refactor for Go — use when implementing any feature, bug fix or behaviour change, before writing implementation code
task-completion
Authoritative completion format for a spec task — the gates to record first, the tasks.md completion entry (heading marker, Status with the PR, Implementation, Spec deviations, Files modified), the hand-off section, the claim-to-evidence table and the task-report block that ends the implementer's final message
synthesize-signals
Read recent GitHub issues, discussions and pull-request feedback with gh, group them into themes, and file new signal entries (and any card proposals) for maintainer approval
spec
Produce a validated spec (requirements, design, tasks, scratchpad) in specs/todo/ from a refined spec or a description, detecting whether the work is one spec or an epic of several
spec-validate
Dispatch a fresh-context code-reviewer to validate spec files against the codebase, the master spec, the invariants and the authoring rules, and return a structured verdict
spec-scope
Decide whether investigated work fits one spec or needs an epic of several, present the determination with its reasons, and take a confirmation or override
spec-resolution
Reference for finding a spec by name across the lifecycle directories, asserting that exactly one copy exists, and moving it between states; the lifecycle skills read it inline, and invoking it resolves one spec
spec-investigate
Ground a planned spec in the codebase before any scoping or writing — the master-spec sections, the invariants, the domains, the existing packages and data flows, and conflicting specs
spec-fix-and-report
Process a spec validation report — apply the fixes that need no judgment, escalate the rest, sweep the spec for stale copies of every changed claim, re-validate, and move a Ready spec to specs/todo/
spec-decomposition
Task-breakdown method for tasks.md — sizing, dependency ordering, budget tiers, Files lists, Domain/agent routing, invariants touched and acceptance-criteria quality, in the task-block format the specs lint enforces
spec-create-single
Write a single spec's requirements.md, design.md, tasks.md and scratchpad.md from the investigation findings, in the format of knowledge/spec-authoring.md
spec-create-epic
Write an epic's master plan (plan.md with a machine-read Work Streams table) and one full spec per work stream, each linked back to the plan
run-spec
Orchestrate every task of a spec to merged pull requests — parse the dependency graph, dispatch each ready task to its pinned agent in its own worktree from origin/main, verify each result against GitHub and the tree, run the review loop, merge, retry within bounds, and move the spec through its lifecycle