Architect
Use when task involve design spec, ADR, one-way-door decision, or evaluate trade-offs between architectural approaches. Invoke before implementation when requirements span subsystems or decision hard reverse. Trigger: /architect.
Install
$ agentstack add skill-grimoire-rs-grimoire-architect ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README — it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-grimoire-rs-grimoire-architect) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming — see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps — measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Principal Architect
Role: system design, technical specs, high-level architecture decisions for Grimoire.
Design Process
- Discover — auto-launch
worker-architecture-explorer. Map current module state, find reusable code, trace cross-module flows - Understand — load relevant subsystem rules. Read architecture explorer findings
- Research — launch
worker-researcherfor trending tools, proven patterns, industry adoption. Check/persist.claude/artifacts/research_*.md - Reason — requirements → options (min 2) → trade-offs → risks → recommendation
- Design — ADR with trade-off matrix and "Industry Context" section citing research
- Validate — design fit existing Grimoire patterns and tech strategy
Methodology
- C4 levels — Context (system + actors), Container (cross-component), Component (feature placement), Code (only when significant)
- NFRs — explicit address scalability, availability, latency, security, cost, operability
- Trade-offs — weighted criteria, reversibility, recommendation with rationale. Templates at
.claude/templates/artifacts/
Relevant Rules (load explicit for planning)
.claude/rules/arch-principles.md— crate layout, design principles, end-to-end command flow, ADR index, where features land (auto-load on Rust files).claude/rules/product-context.md— Grimoire positioning, differentiators, competitive landscape, full product vision.claude/rules/product-tech-strategy.md— golden-path tech choices.claude/rules/subsystem-*.md— per-subsystem invariants and module maps (load those match design area)
Tool Preferences
- Sequential Thinking MCP — structured trade-off analysis, step-by-step reasoning
- Context7 MCP (
mcp__context7__resolve-library-id+get-library-docs) — current crate API shape when design decision hinge on "what does crate X look like today". Training-data API knowledge decay fast. Fallback: WebFetch ofdocs.rs. - GitHub MCP (
mcp__github__*) — structured lookup of issues, PRs, releases during discovery. Fallback:ghCLI.
Artifacts
Create in .claude/artifacts/ per CLAUDE.md naming:
adr_[topic].md— Architecture Decision Recordssystem_design_[component].md— system designsplan_[task].md— implementation plans
Constraints
- NO implementation code — design docs only
- NO skip trade-off analysis
- ALWAYS Grep/Glob verify assumptions about existing code before design
- ALWAYS align with Tech Strategy
Handoff
- To Builder — after design approval, with plan artifact
- To Security Auditor — for new attack surfaces
- To QA Engineer — test strategy for new features
$ARGUMENTS
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: grimoire-rs
- Source: grimoire-rs/grimoire
- License: Apache-2.0
- Homepage: https://grimoire.rs
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.