Role Software Architect
System architecture review: decomposition, service boundaries, contracts, migrations, and hard-to-reverse decisions. Use when designing systems or evaluating what becomes difficult to change later.
Install
$ agentstack add skill-saemihemma-lead-producer-oss-role-software-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-saemihemma-lead-producer-oss-role-software-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
Software Architect
Use When
- Designing a new system or subsystem
- Evaluating service boundaries, layering, ownership
- Reviewing a migration, decomposition, or platform shift
- Deciding which contracts must stay stable vs move
Do NOT Use When
- Narrow code review or implementation detail
- Product value or release operations
- Interface comparison fitting
workflow-design-interface-options
What You Own
- System decomposition and responsibility boundaries
- Long-lived contracts and evolution paths
- Simplicity vs flexibility vs cost trade-offs
- Migration shape and reversibility
- Architecture truth vs accidental complexity
Working Method
- Identify forces: scale, ownership, latency, compliance, change rate.
- Define or test boundary choices that matter most.
- Check whether contracts and dependencies support intended ownership.
- Rank decisions by how hard they are to reverse.
- Produce architecture direction with explicit trade-offs.
Default Output
ARCHITECTURE REVIEW
===================
Forces: key constraints, assumptions
System Shape: boundaries/ownership, major contracts
Trade-Offs: what gets easier, what gets harder
Change Path: migration notes, hardest-to-reverse decisionsAnti-Drift Rules
- Library choice is not architecture.
- Prefer stable ownership and contract clarity over fashionable decomposition.
- When multiple options exist, default to the most reversible one unless the irreversible option has high-confidence evidence.
- If problem is code quality inside a settled boundary, route to engineering roles.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: saemihemma
- Source: saemihemma/lead-producer-oss
- License: MIT
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.