claude

architecture-investigation

Eight-skill methodology for architecture investigations: grill the user until scope is concrete, write a one-page brief, draft a junior-followable plan with a per-item output schema, execute per-item in batched subagents with per-step verification and peer review, then synthesize a recommendation and close with a head-of-architecture review.

0 on GitHubby Thierryupdated 5 months agoengineering
/

Plugin architecture-investigation from marketplace architecture-harness in GROOVIZ/aqzsedrf2. Commands read from the repo's manifest — 1 month ago.

What it installs

Skills (10)

  • grill-the-investigation

    Relentlessly interview the user about an architecture investigation until scope, drivers, methodology, and deliverables are 100% concrete. MUST use AskUserQuestion for every question, multiple-choice only, with a recommended answer. Minimum six questions. Ends with explicit user confirmation. Use wh

  • head-of-architecture-review

    Final senior-architect review of a completed investigation. Reads the brief, the plan, the synthesis, a sample of per-item outputs, and the trace log; returns a written review that an engineering leader would sign — or send back. Use as the closing skill of an investigation, after `synthesize-invest

  • peer-review-brief

    Audit a freshly-written Investigation Brief for gaps, ambiguity, and weak definitions, then close every gap — by re-reading the grilling, re-reading the codebase, or grilling the user again via AskUserQuestion. Iterates until the brief is solid. Invoked by the `/architecture-investigation:investigat

  • peer-review-plan

    Audit a freshly-written investigation plan for gaps — vague verifications, missing schema rows, underweight phases, single-option strategies — then close every gap by re-reading the brief, re-reading the codebase, or grilling the user again via AskUserQuestion. Iterates until the plan is solid. Invo

  • peer-review-step

    Peer-review a verified plan-step output from an engineering-judgment perspective. Reads the step's output, considers what an experienced architect would push back on, and returns improvement suggestions. Use after `verify-step` passes, before moving to the next step.

  • run-investigation-plan

    Execute an APPROVED investigation plan literally — including batched per-item work — using the plan's declared per-item output schema. Refuses to run without `findings/<id>/plan.md` carrying `status: approved`. After every step, runs `verify-step` (correctness) and `peer-review-step` (engineering ju

  • synthesize-investigation

    Roll up per-item findings and strategy options across an entire investigation into a coherent recommendation document. Reads the plan's per-item schema to know which files to consult. Use after `run-investigation-plan` finishes Phase C (cross-item synthesis) and before the head-of-architecture revie

  • verify-step

    Check that a just-completed plan step is grounded, complete against the plan's per-item schema, and free of hallucination. Reads the step's output and the citations it makes, opens the cited files, and confirms the claims hold against the real codebase. Returns a verdict and a list of fixable issues

  • write-investigation-brief

    Produce a one-page Investigation Brief from a CONFIRMED grilling session. Refuses to run without `findings/<id>/grilling.md` carrying `status: confirmed`. The brief is what the user reviews and signs off on before the plan is written.

  • write-investigation-plan

    Turn an APPROVED Investigation Brief into a step-by-step plan a junior architect could execute without further guidance. Refuses to run without `findings/<id>/brief.md` carrying `status: approved`. The plan must declare its own per-item output schema derived from the brief and a falsifiable verifica

Slash commands (1)

  • /architecture-investigation:investigate

    Run an architecture investigation end-to-end through the eight harness skills. Enforces two hard stops with explicit user approval via AskUserQuestion. Never skips grilling.

View source on GitHub

Similar plugins

Matt Pocock's agent skills for real engineering (grilling, spec/ticket flows, TDD, code review, domain modelling and more).

39 skills

mattpocock/skills 323,108

AI-powered codebase understanding — analyze, visualize, and explain any project

9 skills · 10 agents · hooks

Egonex-AI/Understand-Anything 92,410

diagram-design

claudecodex

Editorial diagrams in your brand, as self-contained HTML and SVG. Architecture, flowcharts, sequence, state machines, ER and database schemas, timelines, swimlanes, org charts, Gantt, Wardley maps, user journeys, service blueprints, UML class, lifecycle phase maps, and charts from bar, line and scatter to Sankey, treemap and heatmap, plus many more. Redraws draw.io, Mermaid, Excalidraw and PlantUML files. Exports SVG and PNG.

1 skill · 7 commands

cathrynlavery/diagram-design 66,757

5 skills + 35 modes + Material Passport pipeline. Includes v3.6.7 cross-model audit gate and v3.6.8 generator-evaluator contract.

5 skills · 16 commands · 4 agents · hooks

Imbad0202/academic-research-skills 56,698

Backend API design, GraphQL architecture, workflow orchestration with Temporal, and test-driven backend development

9 skills · 1 command · 8 agents

wshobson/agents 42,461

Long-term semantic memory for Claude Code, powered by OpenViking

5 skills · 1 command · 1 MCP server · hooks

volcengine/OpenViking 42,126

Maintain architecture-investigation?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex pluginslisted