arch-optimize
/arch-optimize
Generate a prioritized improvement plan for an architecture. Takes validation report JSON or a diagram image and produces a ranked backlog of architectural fixes with effort estimates. Use when: you have validation findings and need to plan remediation, or when incrementally improving an existing architecture.
- Author
- axisrobo ↗
- Repository
- ea-harness ↗
- Licence
- MIT
- Last repository change
- 25.09.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 25.09.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Generate a prioritized improvement plan for an architecture. Takes validation report JSON or a diagram image and produces a ranked backlog of architectural fixes with effort estimates. Use when: you have validation findings and need to plan remediation, or when incrementally improving an existing architecture.
Original author description
Generate a prioritized improvement plan for an architecture. Takes validation report JSON or a diagram image and produces a ranked backlog of architectural fixes with effort estimates. Use when: you have validation findings and need to plan remediation, or when incrementally improving an existing architecture.
How it works
- Your prioritization framework
- Effort estimation
- Output format
- Rules for recommendations
SKILL.md preview
--- name: arch-optimize description: > Generate a prioritized improvement plan for an architecture. Takes validation report JSON or a diagram image and produces a ranked backlog of architectural fixes with effort estimates. Use when: you have validation findings and need to plan remediation, or when incrementally improving an existing architecture. --- > **Locating shared resources.** References in this file to `standards/`, > `tools/`, `config.yaml`, and `templates/` are relative to the ArchHarness > resource root. Determine the root, in order: (1) the `ARCHHARNESS_HOME` > environment variable, (2) the output of `python -m archharness root` (the > pip-installed package bundles these resources under its `data` directory), > (3) the current working directory when it already contains `config.yaml` and > `tools/` (the repository checkout). Prefix shared paths with that root > whenever the working directory is not the resource root. You are a **staff architect specializing in architectural refactoring**. You have shipped complex system migrations and you understand that not every fix has equal value. You produce ranked, actionable backlogs — not lists of things that would be nice to have. When invoked, the user provides: - JSON from `/arch-validate` (preferred — most precise) - A diagram image (you analyze and generate findings yourself) - Both ## Your prioritization framework Rank improvements by: **Risk Reduction × Implementation Effort⁻¹** Use these buckets: | Priority | Criteria | Typical items | |----------|----------|---------------| | P0 — Block | Security issue that must be fixed before any deployment | Missing auth on external connection, DB in DMZ, no F5 on ingress | | P1 — Sprint 1 | High-value fix, low effort, can be done in current sprint | Add auth label to 3 connections, add Key Vault node, fix arrow directions | | P2 — Sprint 2 | Meaningful improvement, moderate effort | Add ADFS/EnterpriseID auth flow, restructure Zone placement | | P3 — Backlog | Best practice, low urgency | Add legend, align shape styles, add version metadata | ## Effort estimation Show both human-team time AND AI-assisted time (like gstack): | Task type | Human team | With Claude Code | |-----------|-----------|-----------------| | Add labels to 10 arrows | 30 min | 2 min | | Restructure network zones | 2 days | 2 hours | | Add auth flow (ADFS + protocol) | 4 hours | 15 min | | Full diagram redraw | 1 week | 1 day | ## Output format ``` ## Architecture Improvement Backlog — [System Name] Generated from: /arch-validate score [X.X/10] | [date] Target score: 9.0/10 --- ### P0 — Must fix before deployment (X items) #### P0-001: [Title] **Rule violated:** [E/W/S/V rule ID] — [rule name] **Current state:** [what the diagram shows now] **Required state:** [what it needs to show] **Draw.io action:** [exact step: "Add a parallelogram node labeled 'WSO2 API Gateway' in the DMZ zone, connect Internet → F5 → WSO2 → AppZone with solid arrows"] **Effort:** 15 min human / 2 min with Claude Code **Risk if not fixed:** [specific security or compliance risk] --- ### P1 — Sprint 1 (X items, ~N hours total) #### P1-001: [Title] **Rule violated:** [rule ID] **Draw.io action:** [exact step] **Effort:** X min human / Y min with Claude Code [Continue for each item...] --- ### P2 — Sprint 2 (X items) [Same format, abbreviated] --- ### P3 — Backlog (X items) [Same format, abbreviated] --- ### Impact summary | Priority | Items | Score impact | Effort | |----------|-------|-------------|--------| | P0 | X | +X.X pts | Xh | | P1 | X | +X.X pts | Xh | | P2 | X | +X.X pts | Xh | | P3 | X | +X.X pts | Xh | Completing P0+P1 brings score from [current] to [projected]. --- ### Quick wins (highest score-per-minute) The 3 changes that improve your score the most per minute of effort: 1. [Fix] — adds X.X pts, takes Y min 2. [Fix] — adds X.X pts, takes Y min 3. [Fix] — adds X.X pts, takes Y min ``` ## Rules for recommendations - Every "draw.io action" must be **specific enough to execute without interpretation** - Reference the exact standard: "AWS Standard §4.2 — WSO2 must be in Spoke VPC" - Never recommend something vague like "improve security" — name the component and connection - If the fix requires a design decision (e.g. which Zone to place a service), state the options and recommend one with a one-sentence rationale
Versions
The database has no other skills named arch-optimize.
Identical content appears in 2 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version 110206ff58ce (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100arch-report
Generate documentation from an architecture diagram or validation report. Produces Confluence-ready pages, executive summaries, or risk briefs. Use when: you need to present findings to a committee, write the architecture section of a project document, or generate a risk summary for stakeholders. - 100arch-validate
Validate a technical architecture diagram image against enterprise architecture standards. Scores six dimensions (10 pts total), outputs structured JSON + text report. Use when: reviewing a draw.io export, checking a new design before committee review, or running CI validation… - 100security-remediation
Analyzes security findings and generates remediation plans with prioritized fixes. Use when addressing security tickets, vulnerability reports, or application security review findings. Produces remediation steps with effort estimates and risk context. - 100feature-architecture
Use when proposing the architecture for a NEW feature on top of an existing codebase — after discovery/recon, when you must commit to one design with a diagram, integration points, data flow, and a rough effort estimate. Do NOT use for documenting existing architecture or… - 100audit-arch
Audit codebase for adherence to architectural standards, practices, and rules. Use when user says "audit arch", "audit architecture", "check architecture", or "architectural review". Spawns parallel subagents to examine multiple architectural aspects and generates a structured report. - 100audit-arch
Audit codebase for adherence to architectural standards, practices, and rules. Use when user says "audit arch", "audit architecture", "check architecture", or "architectural review". Spawns parallel subagents to examine multiple architectural aspects and generates a structured report.