メニュー
Build the knowledge indexes from HTML sources: process resources, then graphs and vectors. Use when populating the retrieval indexes an agent queries, as a build-pipeline step run in order before search or graph queries work.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | fit-process |
| description | Build the knowledge indexes from HTML sources: process resources, then graphs and vectors. Use when populating the retrieval indexes an agent queries, as a build-pipeline step run in order before search or graph queries work. |
fit-process is the write surface that turns HTML knowledge sources into the
indexes fit-rag queries. One binary, three subcommands run in order:
resources parses HTML into typed resources, graphs derives an RDF graph from
them, and vectors embeds them into a vector index.
fit-process resourcesfit-process graphsfit-process vectors# Run the stages in order — each reads what the previous produced.
fit-process resources --base https://example.invalid/
fit-process graphs
fit-process vectors
resources accepts --base (-b) to set the base URI for generated
identifiers (default https://example.invalid/). resources and graphs run
offline; vectors calls the embedding service. Run resources before graphs
and vectors, which both read the resource index it writes. Once the indexes
are built, query them with fit-rag.
Prove whether a skill-pack change made agents better at writing code. Use when a single passing eval doesn't prove anything and you need multi-run pass@k evidence, when grading coding tasks with hidden tests the agent cannot see, or when comparing outcomes across skill-set versions.
Create design documents (WHICH/WHERE) for approved specs. A design is a max-200-line architectural sketch — components, interfaces, data flow, and key decisions with trade-offs — that gives reviewers a high-leverage point to redirect architecture before the full plan is written. Design is approved when `wiki/STATUS.md` shows the spec row at `design approved` — written there by a human signal that `kata-dispatch` or the active agent propagates.
Write implementation plans (HOW/WHEN) for approved designs. Translate an approved design into concrete steps, file changes, sequencing, and risks for a trusted agent to execute. Plan is approved when `wiki/STATUS.md` shows the spec row at `plan approved` — `staff-engineer` writes this row after a clean panel review (plans may be approved by agents).
Grade a single artifact (spec, design, plan, or implementation diff) against quality criteria and return findings by severity. Use when another skill spawns a fresh sub-agent for an independent review of its work. This skill never spawns sub-agents — it produces findings only — which structurally prevents the spec/design/plan/implement review loop from recursing.
Write specifications (WHAT/WHY) for features, changes, and improvements. Spec is approved when `wiki/STATUS.md` shows the spec row at `spec approved` — written there by a human signal (label, comment, APPROVED review, or in-session message) that `kata-dispatch` or the active agent propagates. Use when proposing changes, capturing findings as actionable specs, or evaluating spec quality. Pair with the `kata-plan` skill for the HOW side.
Merge gate for open pull requests. Verify contributor trust, classify PR type, rebase on main, fix mechanical CI failures, gate on `wiki/STATUS.md` approval state, and merge passing PRs. Sole external merge point.