一键导入
measure-artifacts
Computes durable implementation metrics for completed features and subfeatures, and can persist a reusable sidecar for later reporting.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Computes durable implementation metrics for completed features and subfeatures, and can persist a reusable sidecar for later reporting.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Bootstraps `.skills/planning.json`, `.skills/execution.json`, and `.skills/conventions.json` for a repository, and can also scaffold a wiki knowledge layer next to the planning feature directory. Use when a user asks to configure a project, initialize `sirius-skills` settings, apply generic defaults, add Jira-oriented conventions, or bootstrap the repo's wiki skeleton.
Canonical workflow for creating and managing durable subfeatures under an existing feature. Use this whenever the user asks to add, create, start, open, or bootstrap a subfeature so downstream planning skills keep the expected metadata and discovery-draft lifecycle.
Reconcile one planning target, optionally execute planning owners in sequence, and persist checkpointed resume context through approval, optional auto-commit handoff, and planning-commit handoff.
Converts repo stories and planning docs into directly executable, dependency-aware work items with traceability and execution handoff.
Closes the active execution slice with validation and records durable closure metadata while invoking shared owner-completion reconciliation.
Produces feature-level system-design.md artifacts before breakdown when a feature needs architecture, interface, constraint, failure-handling, or validation decisions captured durably.
| name | measure-artifacts |
| description | Computes durable implementation metrics for completed features and subfeatures, and can persist a reusable sidecar for later reporting. |
Use this skill when a maintainer wants reusable implementation metrics for a completed feature or subfeature.
implementation-metrics.json only when the caller explicitly asks
for write mode.--scope <path> when nested planning scopes are ambiguoussirius measure-artifacts <target>
sirius measure-artifacts <target> --json
sirius measure-artifacts <target> --write
sirius measure-artifacts <target> --scope apps/payments
--json: machine-readable metrics payload plus sidecar path--write: persist implementation-metrics.json beside the target packetimplemented feature planning or
finalized subfeature metadata).