Architecture Author
incident-io/skills/plugins/incident-io/skills/architecture-authorby incident-ioc8e50a4a7a06No license2 starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated today
Write and maintain architecture docs — the documents that say what each system is, where it runs, what it depends on, and the real names of things (cloud projects, clusters, namespaces, hostnames, buckets). The heart of it is an interview that pins down what each system name actually means before anything is written. Use when asked to write, extend or improve architecture documentation, to document a system, or to fill a gap the `architecture` skill could not answer.
- c8e50a4a7a06Currentcommit c8e50a4Published Oct 8, 2026
Source and attribution
Source:incident-io/skillsinplugins/incident-io/skills/architecture-authorat commitc8e50a4
License: No license
Content belongs to its original authors. SourceWeft indexes it from a public repository.
More from incident-io/skills
Talking To The User
incident-io
How the incident.io skills speak to the person in the session: what the user hears and what goes in the record, ending each reply with one next step, keeping a fixed milestone list through a multi-step job, and using the user's words instead of the skills' own vocabulary. Load it before you reply to the user while running any other incident.io skill.
On Call
incident-io
Explains incident.io on-call schedules, overrides, cover requests and escalation paths, and how to read and change them.
Skill Authoring
incident-io
Create and improve the skills in your own plugins — the ones incident.io's agents and your coding agents load. Use whenever you're writing, editing, or reviewing a skill in any way: creating one, improving one from usage feedback or a review brief, or asking what makes a good skill.
Extensions Review
incident-io
Review what your extensions did over a period: the skill loads that made a real difference, told through the incident or conversation each one happened in, and the incidents no skill or runbook covered. Use whenever anyone wants a review, digest, or pulse of extension or skill usage over a window — "how did our skills do this week", "post yesterday's extensions review to our channel" — one-off or on a schedule. Whether the estate is healthy (sync state, funnels, issues to fix) is the doctor skill, not this one.
Extensions
incident-io
Understand the extensions so that you can help a user configure and manage their incident.io agent estate. Use whenever you're working with incident.io plugins, skills, connectors or MCPs in any way ("I want to set up an incident plugin"), when someone new wants to give incident.io's agents their own knowledge and doesn't yet know the pieces, or when you need to understand the user's existing configuration before editing a plugin or skill.
Doctor
incident-io
Reviews the health of an incident.io agent estate — plugins, skills and connections — and routes each finding to whatever fixes it.
More in Writing & Content
Doc Coauthoring
anthropics
Guides users through a three-stage workflow to co-author documentation, proposals, specs and decision docs.
Writing Guidelines
vercel-labs
Reviews documentation and prose against fetched Writing Guidelines and reports style findings.
Job Post Builder
anthropics
Builds a hiring packet — job post, interview guide with rubrics, and offer letter template — from a role brief.
Write Spec
anthropics
Turns a feature idea or problem statement into a structured PRD with goals, user stories, requirements and metrics.
Draft Content
anthropics
Drafts marketing content such as blog posts, social posts, newsletters, landing pages, press releases and case studies.
Brand Voice Enforcement
anthropics
Applies existing brand voice guidelines to sales and marketing content, then explains the brand choices made.