Describe the runtime behavior of the architecture including major components, request flows, async behavior, and failure paths.
Expected inputs
chosen architecture
main use cases or flows
components/services
operational assumptions
Deliverables
runtime view summary
interaction flow notes
failure and recovery notes
handoff recommendation
Trigger this skill when
You need to move from vague architectural preference to explicit design reasoning.
Structural decisions, boundaries, or quality goals are unclear or contested.
A team needs an architecture artifact, critique, or decision record that can drive implementation.
Operating procedure
Clarify the decision or structure this skill is meant to address.
Separate facts, assumptions, constraints, and desired quality outcomes.
Produce concrete structure or analysis tied to this system context.
Make tradeoffs and uncertainty explicit instead of hiding them behind generic architecture language.
Recommend the next most useful architecture artifact or decision step.
Quality gates
Recommendations are tied to system context and drivers.
Assumptions and unknowns are visible.
Operational and deployment consequences are not ignored when relevant.
Findings are concrete enough to influence implementation or governance.
Output style
Be concrete and structured.
Prefer architecture rationale over buzzwords.
Separate evidence, inference, and recommendation.
Use priority or severity when useful.
Failure modes to avoid
Do not recommend a style because it sounds modern.
Do not hide uncertainty behind definitive language.
Do not ignore team size, ownership, or operational cost.
Do not produce diagrams or structure with no stated purpose.
Minimum output skeleton
## Summary
## Findings or proposal
## Evidence vs assumptions
## Risks or tradeoffs
## Recommended next skill
Handoff targets
deployment-view-writer
availability-strategy-reviewer
quality-attribute-scenario-writer
1---2name: runtime-view-writer3description: runtime-view-writer4---5# runtime-view-writer67## Purpose8Describe the runtime behavior of the architecture including major components, request flows, async behavior, and failure paths.910## Expected inputs11- chosen architecture12- main use cases or flows13- components/services14- operational assumptions1516## Deliverables17- runtime view summary18- interaction flow notes19- failure and recovery notes20- handoff recommendation2122## Trigger this skill when23- You need to move from vague architectural preference to explicit design reasoning.24- Structural decisions, boundaries, or quality goals are unclear or contested.25- A team needs an architecture artifact, critique, or decision record that can drive implementation.2627## Operating procedure281. Clarify the decision or structure this skill is meant to address.292. Separate facts, assumptions, constraints, and desired quality outcomes.303. Produce concrete structure or analysis tied to this system context.314. Make tradeoffs and uncertainty explicit instead of hiding them behind generic architecture language.325. Recommend the next most useful architecture artifact or decision step.3334## Quality gates35- Recommendations are tied to system context and drivers.36- Assumptions and unknowns are visible.37- Operational and deployment consequences are not ignored when relevant.38- Findings are concrete enough to influence implementation or governance.3940## Output style41- Be concrete and structured.42- Prefer architecture rationale over buzzwords.43- Separate evidence, inference, and recommendation.44- Use priority or severity when useful.4546## Failure modes to avoid47- Do not recommend a style because it sounds modern.48- Do not hide uncertainty behind definitive language.49- Do not ignore team size, ownership, or operational cost.50- Do not produce diagrams or structure with no stated purpose.5152## Minimum output skeleton53```md54## Summary55## Findings or proposal56## Evidence vs assumptions57## Risks or tradeoffs58## Recommended next skill59```6061## Handoff targets62- deployment-view-writer63- availability-strategy-reviewer64- quality-attribute-scenario-writer
Run npx skillmds@latest add 45ck/runtime-view-writer in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
runtime-view-writer It is listed under Coding & Dev Tools on SkillMD.
This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
45ck (@45ck) published this skill. Their other Agent Skills are listed on their SkillMD profile.
45ck