eng-design-doc-review

Dispatch a read-only subagent to audit technical design documents.

8|1|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/bostonaholic/team --skill eng-design-doc-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eng-design-doc-review
Source: https://github.com/bostonaholic/team/tree/main/skills/eng-design-doc-review
Command: npx skills add https://github.com/bostonaholic/team --skill eng-design-doc-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the risk of self-evaluation bias in technical design by providing an independent, fresh-context adversarial review of design documents.

Core Features & Use Cases

  • Independent Audit: Dispatches a read-only subagent to evaluate design documents without shared conversation history.
  • Methodology Enforcement: Validates designs against engineering standards, ADR-quality criteria, and edge-case coverage.
  • Use Case: Use this skill to verify that a new system architecture document is robust, well-justified, and covers all necessary edge cases before implementation begins.

Quick Start

Ask the team to review the design document located in the current plans directory.

Frequently Asked Questions about eng-design-doc-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit technical design documents for structural integrity and edge-case coverage?

Audit technical design documents by dispatching a read-only subagent to independently verify structural integrity, decision justification, and edge-case coverage against engineering standards.

What is adversarial review in software architecture design?

Adversarial review uses an independent, fresh-context subagent to evaluate design documents, mitigating self-evaluation bias by validating architecture decisions and edge-case coverage.

How do I review system architecture documents before implementation begins?

Review system architecture documents by operating on design artifacts within project worktrees, enforcing ADR-quality criteria and conventional comment formatting to provide actionable feedback.

Does the design review process work on artifacts inside project worktrees?

Yes, the design review process operates directly on design artifacts located within project worktrees to verify structural integrity and decision justification without shared conversation history.

Can I validate ADR-quality criteria and edge-case coverage in my technical designs?

Yes, you can validate ADR-quality criteria and edge-case coverage by enforcing engineering standards during the independent subagent audit of your technical designs.

When should I use an independent subagent for design document review?

Use an independent subagent for design document review when you need to eliminate self-evaluation bias and require a fresh-context, read-only audit of your architecture decisions.