{
  "checklist_items": [
    {
      "id": "chk_autonomous_write_test_iterate",
      "item": "The Product Design team uses an autonomous-loop pattern: Claude writes code, runs tests, and iterates continuously, with a human reviewing only the final result.",
      "category": "autonomous_loop",
      "source_title": "How Anthropic teams use Claude Code",
      "source_url": "https://claude.com/blog/how-anthropic-teams-use-claude-code",
      "summary": "Autonomous coding loops close the write-test-iterate cycle without a human in every step, only at final review.",
      "created_at": "2026-07-02 06:02:48",
      "cite_as": "https://subagentchecklists.com/api/checklist-items/chk_autonomous_write_test_iterate"
    },
    {
      "id": "chk_claude_md_first_stop",
      "item": "Anthropic's own Product Engineering team calls Claude Code their \"first stop\" for any task; new data scientists on Infra feed Claude Code their entire codebase so it can find the relevant CLAUDE.md files and explain dependencies.",
      "category": "context_file",
      "source_title": "How Anthropic teams use Claude Code",
      "source_url": "https://claude.com/blog/how-anthropic-teams-use-claude-code",
      "summary": "CLAUDE.md-driven context lets Claude read a repo's own documentation to find relevant files and explain dependencies instead of needing a separate data-catalog tool.",
      "created_at": "2026-07-02 06:02:48",
      "cite_as": "https://subagentchecklists.com/api/checklist-items/chk_claude_md_first_stop"
    },
    {
      "id": "chk_debugging_via_evidence_feeding",
      "item": "Security Engineering and Data Infrastructure teams debug production issues by feeding Claude Code stack traces and screenshots directly, rather than describing the problem from memory.",
      "category": "documentation_runbook",
      "source_title": "How Anthropic teams use Claude Code",
      "source_url": "https://claude.com/blog/how-anthropic-teams-use-claude-code",
      "summary": "Feeding raw evidence (stack traces, screenshots) into context produces more reliable debugging runbooks than paraphrased problem descriptions.",
      "created_at": "2026-07-02 06:02:48",
      "cite_as": "https://subagentchecklists.com/api/checklist-items/chk_debugging_via_evidence_feeding"
    },
    {
      "id": "chk_runbook_consolidation",
      "item": "The Security Engineering team has Claude \"ingest multiple documentation sources to create markdown runbooks and troubleshooting guides\" -- condensed docs become context for debugging, which they found more efficient than searching full knowledge bases.",
      "category": "documentation_runbook",
      "source_title": "How Anthropic teams use Claude Code",
      "source_url": "https://claude.com/blog/how-anthropic-teams-use-claude-code",
      "summary": "Consolidating scattered docs into a single dated runbook (with citations back to sources) beats searching a full knowledge base each time.",
      "created_at": "2026-07-02 06:02:48",
      "cite_as": "https://subagentchecklists.com/api/checklist-items/chk_runbook_consolidation"
    },
    {
      "id": "chk_sandbox_84_percent",
      "item": "Sandboxing reduces permission prompts by 84% in Anthropic's own internal usage.",
      "category": "sandboxing",
      "source_title": "Making Claude Code more secure and autonomous with sandboxing",
      "source_url": "https://www.anthropic.com/engineering/claude-code-sandboxing",
      "summary": "The measured impact of the sandbox boundary model: an 84% reduction in permission prompts.",
      "created_at": "2026-07-02 06:02:48",
      "cite_as": "https://subagentchecklists.com/api/checklist-items/chk_sandbox_84_percent"
    },
    {
      "id": "chk_sandbox_notify_on_escape",
      "item": "If Claude tries to access something outside the sandbox boundary, the user is notified immediately and can choose whether to allow it -- the boundary lets Claude act freely inside it while still surfacing any attempted escape.",
      "category": "sandboxing",
      "source_title": "Making Claude Code more secure and autonomous with sandboxing",
      "source_url": "https://www.anthropic.com/engineering/claude-code-sandboxing",
      "summary": "Escape attempts are surfaced immediately for a human decision, rather than either silently blocked or silently allowed.",
      "created_at": "2026-07-02 06:02:48",
      "cite_as": "https://subagentchecklists.com/api/checklist-items/chk_sandbox_notify_on_escape"
    },
    {
      "id": "chk_sandbox_os_primitives",
      "item": "The sandbox is built on OS-level security primitives -- Linux bubblewrap and macOS Seatbelt -- to enforce filesystem and network restrictions at the OS level, not just in the application layer.",
      "category": "sandboxing",
      "source_title": "Making Claude Code more secure and autonomous with sandboxing",
      "source_url": "https://www.anthropic.com/engineering/claude-code-sandboxing",
      "summary": "Enforcement happens at the OS level (bubblewrap on Linux, Seatbelt on macOS), which is stronger than an app-level permission check alone.",
      "created_at": "2026-07-02 06:02:48",
      "cite_as": "https://subagentchecklists.com/api/checklist-items/chk_sandbox_os_primitives"
    },
    {
      "id": "chk_sandbox_prompt_injection_defense",
      "item": "Filesystem isolation is particularly important in preventing a prompt-injected Claude from modifying sensitive system files; network isolation prevents a prompt-injected Claude from leaking sensitive information or downloading malware.",
      "category": "sandboxing",
      "source_title": "Making Claude Code more secure and autonomous with sandboxing",
      "source_url": "https://www.anthropic.com/engineering/claude-code-sandboxing",
      "summary": "The two boundaries exist specifically as a defense against prompt-injection attacks attempting to escape the working directory or exfiltrate data.",
      "created_at": "2026-07-02 06:02:48",
      "cite_as": "https://subagentchecklists.com/api/checklist-items/chk_sandbox_prompt_injection_defense"
    },
    {
      "id": "chk_sandbox_two_boundaries",
      "item": "Anthropic's Claude Code sandboxing draws two boundaries -- filesystem isolation (read/write confined to the working directory) and network isolation (an allowlist of domains via a proxy) -- so Claude can act freely inside the boundary without asking permission for every step, and is flagged immediately if it tries to leave it.",
      "category": "sandboxing",
      "source_title": "Making Claude Code more secure and autonomous with sandboxing",
      "source_url": "https://www.anthropic.com/engineering/claude-code-sandboxing",
      "summary": "The core two-boundary model: filesystem confinement to the working directory, and network confinement to an allowlist via a proxy.",
      "created_at": "2026-07-02 06:02:48",
      "cite_as": "https://subagentchecklists.com/api/checklist-items/chk_sandbox_two_boundaries"
    },
    {
      "id": "chk_feedback_loop_quality",
      "item": "Giving Claude a way to verify its work will markedly improve the quality of the final result; if Claude can close the feedback loop on its own, it will iterate until the output is right.",
      "category": "verification_gate",
      "source_title": "Claude Cowork task list verification gate (web search, 2026-07-02)",
      "source_url": "https://support.claude.com/en/articles/13345190-get-started-with-claude-cowork",
      "summary": "A closable feedback loop (build/test/lint the agent can run itself) is what allows an agent to self-correct rather than needing a human to catch every error.",
      "created_at": "2026-07-02 06:02:48",
      "cite_as": "https://subagentchecklists.com/api/checklist-items/chk_feedback_loop_quality"
    },
    {
      "id": "chk_review_80_percent",
      "item": "Engineers give Claude abstract problems they're unfamiliar with, let it work autonomously, then review the roughly 80%-complete solution before taking over for final refinements.",
      "category": "verification_gate",
      "source_title": "How Anthropic teams use Claude Code",
      "source_url": "https://claude.com/blog/how-anthropic-teams-use-claude-code",
      "summary": "A human verification checkpoint at ~80% completion, not at every step, is how some Anthropic engineers gate autonomous work.",
      "created_at": "2026-07-02 06:02:48",
      "cite_as": "https://subagentchecklists.com/api/checklist-items/chk_review_80_percent"
    },
    {
      "id": "chk_security_review_github_action",
      "item": "Anthropic provides an AI-powered security review GitHub Action using Claude to analyze code changes for security vulnerabilities in context, producing detailed explanations, severity ratings, and remediation guidance.",
      "category": "verification_gate",
      "source_title": "anthropics/claude-code-security-review (GitHub)",
      "source_url": "https://github.com/anthropics/claude-code-security-review",
      "summary": "A CI-integrated verification gate: a GitHub Action that runs Claude-based security review on every code change, with severity-rated findings.",
      "created_at": "2026-07-02 06:02:48",
      "cite_as": "https://subagentchecklists.com/api/checklist-items/chk_security_review_github_action"
    },
    {
      "id": "chk_security_review_three_stages",
      "item": "Anthropic's Claude Code security-guidance plugin runs a three-stage code review: a lightweight pattern check during file edits (no model call), a deeper review when Claude performs commits or pushes via the Bash tool that checks surrounding files/sanitizers/related code paths to reduce false positives, and a final catch for issues like injection flaws, unsafe deserialization, and insecure DOM APIs.",
      "category": "verification_gate",
      "source_title": "Claude now reviews and fixes vulnerabilities as you write code (Help Net Security, 2026-05-27)",
      "source_url": "https://www.helpnetsecurity.com/2026/05/27/anthropic-claude-code-security-guidance-plugin/",
      "summary": "A layered review pattern -- cheap pattern checks on every edit, a deeper model-backed review at commit/push time -- catches security issues before they reach a pull request.",
      "created_at": "2026-07-02 06:02:48",
      "cite_as": "https://subagentchecklists.com/api/checklist-items/chk_security_review_three_stages"
    },
    {
      "id": "chk_verification_before_complete",
      "item": "A verification-gate pattern should confirm a test/build/typecheck command exists for the detected project type and was actually run in the current session (an exit-code-0 log, not just \"tests exist\"), and should refuse to mark a task complete if changed files have no corresponding check run.",
      "category": "verification_gate",
      "source_title": "agentic-dev-practices skill (this repo)",
      "source_url": "https://www.anthropic.com/engineering/claude-code-sandboxing",
      "summary": "A real verification gate checks that a build/test/typecheck command was actually executed this session against the changed files -- not merely that such a command exists in the repo.",
      "created_at": "2026-07-02 06:02:48",
      "cite_as": "https://subagentchecklists.com/api/checklist-items/chk_verification_before_complete"
    }
  ]
}