/

/architect-refine-critique

by Nick Tunentcoding/claude-skillz351 stars

Three-phase design review. Chain architect → refiner → critique subagents. Triggers on: 'design review', 'architecture review', '/arc', system design proposals, significant refactoring decisions, new service or module design.

7 files
22.7 KB
Updated 8 months ago
GitHub
1 warning

Ask your Agent

Use this Skill: https://skilld.dev/gh/ntcoding/claude-skillz/architect-refine-critique

This session only. Nothing lands on disk.

SKILL.md

840 B raw

≈64 tokens always: the name and description. ≈135 when used: this file. ≈5.6k more on demand in 6 files.

Architect-Refine-Critique

Chain three subagents sequentially from the main conversation.

Usage

/arc [name] [target]

Execution

Use the architect subagent to create the initial design for [target] with name=[name], then use the refiner subagent to improve the design with name=[name], then use the critique subagent to challenge the design with name=[name].

After all three complete, tell the user: "Run /arc-review [name] to discuss findings."

Do not analyze. Do not summarize. Do not add value. Just chain and hand off.

Source: SKILL.md on GitHub

Third-party checks

1 warning7d4 checks · Risk SAFE

Gen Agent Trust Hub7d
The skill implements an automated architecture review workflow involving Architect, Refiner, and Critique stages. It utilizes standard project analysis tools such as npx and reads codebase files. The primary security observation is a low-risk indirect prompt injection surface where the agent processes external PRDs and source code that could contain adversarial instructions.
Socket7d
No alerts
Snyk7d
Risk: LOW · No issues
Runlayer7mo
7/7 files flagged

Provenance

Signed by skilld at f9e68f5. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 2 months ago.

Dormantupdated 8 months ago

Capability

version: 1.3.6