メニュー
Sidecar data for /logs workflow — conditional audit templates loaded just-in-time when plan methodology requires specialized compliance checks.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Companion skill for the /open workflow. Automates workspace diagnostic steps when starting a new session on a project. Collects active session status, project contracts, active task metrics, compact memory presence, roadmap phases, pending brainstorms, and git status.
Sidecar data for /brainstorm workflow — Brainstorm (open), Decision (finalized), and Research document templates loaded just-in-time.
Sidecar data for /docs workflow — document templates loaded just-in-time when generating docs.
Modular HTML rendering engine for PARA Workspace. Converts Markdown documents, code graphs, and standalone files into interactive, self-contained HTML pages with consistent Notion-inspired theming. Triggers when the user asks to compile docs to HTML, render graph visualization, export markdown to HTML, view docs statically, or preview documents.
Sidecar data for /plan workflow — Detail Plan and Roadmap templates loaded just-in-time.
Sidecar data for /qa workflow — Red Team personas, dimension checklists, and QA report templates loaded just-in-time.
| name | Logs Audit Extensions |
| description | Sidecar data for /logs workflow — conditional audit templates loaded just-in-time when plan methodology requires specialized compliance checks. |
| source | user |
Sidecar Skill for the
/logsworkflow. Contains audit extension templates that the Agent loads only when the session used a specialized plan template (e.g., TDD plan → load TDD Compliance template).Pattern: Workflow = Logic → Sidecar Skill = Data Router. The
/logsworkflow instructs the Agent to read this skill at audit extension time.
/logs --deep → Step 3: After base audit sections, check if session used a TDD plan → load references/tdd-compliance.md/logs (fast glance) → NOT needed (no extensions)IF active_plan exists in project.md:
Read the plan file → check for "Methodology: Strict TDD" or plan filename contains "-tdd"
OR check if plan template used TDD Cycle markers (🔴 RED / 🟢 GREEN)
→ IF match: load references/tdd-compliance.md and append to audit report
ELSE:
Skip TDD compliance section
| Resource | Relative Path | Description |
|---|---|---|
| TDD Compliance Template | references/tdd-compliance.md | Audit template for verifying Red-Green-Refactor order from conversation log and git history |
| Transcript Parser | scripts/parse-transcript.py | Python script to parse Antigravity session transcript locally for tool counts, commands, and mutated files |
When executing /logs --deep or verifying TDD/Drift compliance, the Agent can run this Python utility locally to extract structured statistics without flooding the token context window:
# Resolve and run from workspace root
python3 .agents/skills/logs/scripts/parse-transcript.py [path_to_transcript_or_directory]
Convention: Data files live in
references/(nottemplates/). This follows the Sidecar Skill convention formalized in v1.7.6.3.
Future audit extensions can be added here following the same pattern:
| Plan Methodology | Detection Marker | Template (planned) |
|---|---|---|
| TDD | 🔴 RED / 🟢 GREEN markers in plan | ✅ tdd-compliance.md |
| Spec-Driven | /spec reference in plan | ⏳ spec-compliance.md |
| Security-First | SECURITY harness guards | ⏳ security-audit.md |