survey-code

Investigate the codebase related to the given task.

Procedure

Step SVC-0 — Resolve <PLANS_DIR>

Before any tool call below that references <PLANS_DIR>, run the following Bash command exactly once:

PLANS_DIR=$(bash "$AGENTS_CONFIG_DIR/bin/workflow-plans-dir" 2>/dev/null \
              || printf '%s\n' "${WORKFLOW_PLANS_DIR:-$HOME/.workflow-plans}")
printf 'PLANS_DIR=%s\n' "$PLANS_DIR"

Capture the printed absolute path and substitute it for every <PLANS_DIR> placeholder in the remainder of this SKILL.md. Subagent prompts must receive the resolved absolute path as a literal string (subagents cannot expand $VAR). Reuse across all subsequent steps in this skill invocation — do not re-resolve.

When invoked as a parallel Agent subagent by workflow-init, the orchestrator passes artifact_path and context_path as resolved absolute strings — use those instead of running Step SVC-0.

Canonical documentation: skills/_shared/resolve-plans-dir.md.

SVC-1. Claim extraction (run before reading any code): Input precedence (read whichever exists first): (a) <PLANS_DIR>/<session-id>-intent.md — preferred (post-clarify-intent calls) (b) <PLANS_DIR>/<session-id>-context.md — fallback (pre-clarify-intent calls from workflow-init; use "User initial prompt" and "Issue body" sections) If neither exists: proceed to Step SVC-2 with an empty claim list. Extract up to 5 behavioral/factual claims from Background/Motivation and Scope. Target: "X is blocked", "X does Y", "X is broken", "X cannot Z". Exclude aesthetic claims and pure preferences. Works with Japanese and English content.

SVC-2. Identify candidate files and areas using Glob and Grep. SVC-3. Read relevant source files, configs, tests, and docs. SVC-4. For each claim extracted in Step SVC-1, verify it against the current codebase:

• verdict: holds — evidence in code confirms the claim
• verdict: contradicted — evidence in code contradicts the claim
• verdict: indeterminate — insufficient evidence to confirm or deny SVC-5. Summarize: existing patterns, architectural constraints, relevant files (with line numbers), and anything that affects implementation. SVC-6. Write findings to <PLANS_DIR>/<session-id>-survey-code.md. The file must include a ## Verified Claims section:

## Verified Claims
- claim: <text from intent.md>
  verdict: holds | contradicted | indeterminate
  evidence: <file:line or "no matching code found">

If no claims were extracted in Step SVC-1, write the section with the note "No verifiable behavioral/factual claims found in intent.md or context.md."