architecture

Solid

Create or update technical architecture after the spec is stable and before execution planning.

Code & Development 3 stars 0 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 82/100

Stars 20%
20
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Architecture assessment and authoring ## Workflow role - role_name: architecture - stage: authoring - upstream: approved spec and current spec review - downstream: architecture-review - summary: Assess architecture impact and author the smallest justified package. - ownership: Architecture artifacts and authorized architecture authoring evidence only. - must_not_claim: architecture-review approval, plan readiness, implementation readiness, verification, branch readiness, release readiness, or PR readiness. Portable work is isolated. Workflow-managed execution does not enlarge the architecture write set. ## Evidence and upstream settlement Read current guidance, proposal, approved spec/review, canonical architecture, relevant ADRs, project map, and affected system surfaces. Rank governing artifacts above history and inference; upstream artifacts and state are read-only. Require an approved current spec without later contradiction or open resolution. Route unsettled direction to `proposal`, unclear behavior to `spec`, and missing settlement to `spec-review`. ## Classification and loaded assemblies Classify before mutation. Assessment mode is `isolated` or `workflow-managed`; applicability judgment is `required`, `not-required`, or `ambiguous`; route result is `architecture-required`, `architecture-not-required`, or `architecture-ambiguous`; authoring action is `assessment-only`, `canonical-update`, `adr-only`, `canonical-update-with-adr`, or `blocked`. | Assembly | U...

Details

Author
xiongxianfei
Repository
xiongxianfei/rigorloop
Created
4 months ago
Last Updated
yesterday
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Listed

architecture-review

Review a proposed architecture/design before execution planning. Use for cross-component, hard-to-reverse, data, security, performance, migration, or long-lived design decisions.

3 Updated yesterday
xiongxianfei
AI & Automation Listed

write-architecture

Write an ARCHITECTURE doc (HTML) for a system, or a CHANGE_REQUEST (Markdown) for a scoped change on top of an existing one. Use when the user asks for "the architecture", "how it's built", or "a change request / CR".

0 Updated 2 days ago
dsivov
AI & Automation Listed

software-architecture

Assess, design, review, and evolve general software architecture with explicit system boundaries, responsibilities, data and integration contracts, quality attributes, operational concerns, and migration paths. Use when a user asks for software or system architecture, architecture options or review, service or module boundaries, monolith versus service decisions, scalability, reliability, deployability, operational readiness, performance objectives, load, soak, or stress objectives, workload scenarios, and capacity decisions, or non-frontend testing-strategy design such as the test pyramid, coverage goals, and which risks get which test types. Apply Twelve-Factor practices where they fit a long-running service; do not use for frontend-only architecture, codebase audit-only work, implementation plans, execution of an existing repository check, or recording an already-made decision when a narrower skill applies.

0 Updated today
sebastian-software