spec
specは、アイデアからの新規生成、コードからの抽出、バグ処理による更新、既存仕様の修正を通じて、技術仕様の管理を強力に支援します。これにより、仕様とコードの同期を保ち、ソフトウェア開発の明確さと効率を向上させます。
npx skills add https://github.com/juliusbrussee/cavekit --skill specBefore / After 効果比較
1 组エンジニアが手動でコードを分析し、問題を特定して技術仕様を更新するため、時間がかかりエラーが発生しやすく、仕様と実際のコードの間に不一致が生じ、開発効率に影響を与えていました。
AIスキルを使用してバグの説明とコードを自動的に分析し、SPEC.mdの関連セクションを迅速に特定して更新することで、仕様更新の効率と精度が大幅に向上します。
spec — spec mutator
Read FORMAT.md at repo root if not already loaded. Caveman skill applies to all writes here.
DISPATCH
Inspect user request and project state:
- No
SPEC.mdat repo root AND args describe idea → NEW - No
SPEC.mdANDfrom-codein args → DISTILL SPEC.mdexists AND args startbug:→ BACKPROPSPEC.mdexists AND args startamend→ AMENDSPEC.mdexists, no args → ask user which mode
NEW — idea → spec
Input: user idea.
Steps:
- Extract goal (1 line, caveman). → §G.
- List constraints user stated or implied. → §C.
- List external surfaces user named. → §I.
- Propose initial invariants. → §V (numbered V1…).
- Break goal into ordered tasks. → §T pipe table, all status
., ids T1… - §B section with header row only (
id|date|cause|fix).
Write to SPEC.md. Show user full file. Ask: "spec OK? suggest edits or invoke build."
DISTILL — code → spec
Walk repo. Produce §G (infer from README/package.json/main entry), §C (infer from stack), §I (enumerate public APIs/CLIs/configs), §V (derive from tests and assertions), §T (one task per known TODO or missing test), §B (empty).
Caveman everywhere. Flag uncertain items with ? in text so user can confirm.
BACKPROP — bug → §B + §V
Input: bug: <description>.
Steps:
- Parse bug description.
- Find root cause (read relevant code).
- Decide: would a new invariant catch recurrence? If yes → draft
V<next>. - Append §B row:
B<next>|<date>|<cause>|V<N>. - Append new invariant to §V.
- If fix also changes behavior → add/update §T rows.
- Show diff. Apply only on user OK.
Rule: every bug gets a §B entry. Invariant optional but preferred.
AMEND — targeted edit
Input: amend §V.3 or amend §T etc.
Read that section. Show current. Ask user what changes. Write. Show diff.
Never silently rewrite sections user did not name.
OUTPUT RULES
- Caveman format per
FORMAT.md. - Preserve identifiers, paths, code verbatim.
- Numbering monotonic — never reuse §V.N or §B.N.
- §T row
citescolumn ! list §V/§I deps:T5|.|impl auth mw|V2,I.api.
NON-GOALS
- No sub-agents. Main thread writes.
- No dashboards, no logs, no state files beyond SPEC.md itself.
- No auto-build after spec. User invokes build explicitly.
ユーザーレビュー (0)
レビューを書く
レビューなし
統計データ
ユーザー評価
この Skill を評価