skill-wfukatsu-nexus-architect-analyze · by Install
$ agentstack add skill-wfukatsu-nexus-architect-analyze ✓ 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-wfukatsu-nexus-architect-analyze) 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
System Analysis
Outcome
Structure the domain knowledge of the target system and generate the following four analysis documents:
- System Overview — Business context, key features, system boundaries
- Ubiquitous Language — Domain term dictionary (term, definition, code correspondence, usage context)
- Actors, Roles, and Permissions — User types, role definitions, permission matrix
- Domain-Code Mapping — Correspondence between domain concepts and code implementations
Judgment Criteria
- Cross-reference ubiquitous language with actual naming in the code
- Detect cases where the same concept uses different names
- Identify gaps in domain-code mapping (domain concepts not reflected in code)
- Track where business rules are implemented in the code
Prerequisites
| File | Required/Recommended | Source | |------|---------------------|--------| | reports/before/{project}/ | Required | /architect:investigate |
Available Resources
- Serena MCP — Symbol relationship analysis via
find_symbol,find_referencing_symbols(preferred) - Glob/Grep — Search for domain terms within code
- Read — Extract domain knowledge from documentation, comments, and test cases
- Task(Explore) — Parallel entity extraction across large codebases
Output
| File | Content | |------|---------| | reports/01_analysis/system-overview.md | Business context, feature list | | reports/01_analysis/ubiquitous-language.md | Domain term dictionary | | reports/01_analysis/actors-roles-permissions.md | Actor, role, and permission matrix | | reports/01_analysis/domain-code-mapping.md | Domain-code correspondence table |
Write all reports in the language configured in work/pipeline-progress.json (options.output_language).
Completion
- All four output files have been written
- Ubiquitous language contains at least 20 domain terms
- Update pipeline-progress.json
Related Skills
| Skill | Relationship | |-------|-------------| | /architect:investigate | Upstream (input source) | | /architect:evaluate-mmi | Downstream | | /architect:evaluate-ddd | Downstream | | /architect:analyze-data-model | Downstream |
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: wfukatsu
- Source: wfukatsu/nexus-architect
- 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.