メニュー
Where project tasks/TODOs live and how to track them - the /vault/Tasks/<area>/ directory with open/active/closed/dropped lifecycle pages. Use whenever you would record a TODO, start/finish a task, or are tempted to create a TASKS.md or TODO.md next to code.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | tasks |
| description | Where project tasks/TODOs live and how to track them - the /vault/Tasks/<area>/ directory with open/active/closed/dropped lifecycle pages. Use whenever you would record a TODO, start/finish a task, or are tempted to create a TASKS.md or TODO.md next to code. |
READ FIRST: /vault/Tasks/INDEX.md (the master index IS the authority for this convention).
All task tracking lives in /vault/Tasks/<area>/. Each area has INDEX.md plus four
lifecycle pages: open.md (not started), active.md (in progress),
closed.md (done), dropped.md (ended without completing).
The rule agents break: never create a TASKS.md / TODO.md / *_TODO.md
next to code. That scatter is what /vault/Tasks/ replaces. A note-to-self goes in
/vault/Tasks/<area>/open.md, not in a new file beside the module.
Move a task by CUTTING its block between pages (never copy - one state only),
and keep its **Status:** line dated. closed = done; dropped = decided not
to do it - keep them apart so history stays honest.
Migration is in progress (tracked as TOOL-001 in vault/Tasks/tooling/active.md):
amba is migrated; other areas' rows in /vault/Tasks/INDEX.md are marked pending
and still point at their old file until moved.
##/### as a header when NOT inside a ``` code fence — task
bodies embed markdown/code examples whose lines start with ##, and a naive
split silently drops the tail of those tasks.**Status:** marker. Verify
each task against the tree (does the file/feature exist, did the work land?).
The amba pilot's "active" bucket was mostly already done. closed = done,
dropped = decided-against.INDEX.md + open/active/closed/dropped.md (see vault/Tasks/amba/ for the
shape). Keep each task block intact; drop only scaffolding (legends, phase
headers, stale summary tables).Enforcement authority remains /GLOBAL_REQUIREMENTS.md. Design/DV/FPGA practice lives in the handbook (vault/handbook/INDEX.md), not here - this tracks WORK.
Authoring a per-module reference page under docs/markdown (RTLCommon/RTLMath/RTLAmba) - the local .md style (header table, Overview, Architecture, Top-level Interface, Data model, Timing, Related, Test) and the SV header block that mirrors it. Use whenever you add or change an RTL block and need its docs/markdown page, and keep the book index in sync.
What kind of documentation lives where in this repo - handbook (method) vs docs/markdown (reader-facing) vs vault/Tasks (work) vs beside-code (CLAUDE.md, PRD). The rule that a beside-code README is a link, never a standalone guide, and that style guides / how-tos never live in the RTL tree. Use before creating, moving, or "tidying" any .md file, and when reviewing an area's meta-docs.
Coverage methodology - Verilator line/toggle coverage per component, functional coverage expectations, and the monbus packet-type coverage matrix. Use when adding tests, closing coverage, or preparing a board-gate sign-off.
The Sherpa documentation pipeline - md_to_docx with --style, LoF/LoT/LoW caption encoding, book indexes, RTL PDF generation, HAS/MAS vs operator guides. Use before generating or restructuring any deliverable doc.
Filelist rules - EVERY module MUST have a .f and MUST be registered in bin/filelists.toml. Components own their compile closure, consumers -f include, never hand-list another area's sources. Use when adding ANY new RTL module, test, or .f file.
Formal verification flow - SymbiYosys via sv2v flatten, in-RTL ifdef FORMAL properties, mutation-checking every new assertion, harness vacuity traps. Use when writing properties, regenerating proofs, or after changing any module with a formal dir.