# Document Architecture Before Writing Specifications

Vague architecture leaves teams with incompatible interfaces and undocumented decisions. This skill structures architecture, decisions, contracts, and component designs for human review before specification.

## Install

```bash
npx skillstore add atri10/executor-architecture
```

## Metadata

- Status: approved
- Slug: atri10-executor-architecture
- Skillstore revision: r1
- Version status: missing
- Tree hash: cd1cf0b4d5a2d3cc5bf8d3dc8da99597964cc8c6147a69672e517af921e5352b
- Author: atri10
- GitHub username: atri10
- License: MIT
- Repository: https://github.com/atri10/executor/tree/39ddcfe1d9f3497102622b72aa235fb0770187fe/skills/executor-architecture
- Ref: 6d0b11444384184b7ae743742a7e233a9a705cd9
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: filesystem, external\_commands
- Quality score: 50
- Quality tier: warning
- Public page: https://skillstore.pages.dev/skills/atri10-executor-architecture
- Manifest: https://skillstore.pages.dev/api/skills/atri10-executor-architecture/manifest

## Capabilities

- Draft architecture documents covering constraints, components, dependency boundaries, data flow, failure modes, and deployment.
- Record decisions with viable alternatives, accepted costs, observable reversal criteria, and reversibility labels.
- Specify interface signatures, types, errors, lifecycle rules, stability states, and named consumers.
- Describe component state, algorithms, edge cases, test dependencies, and file responsibilities.
- Maintain document links, initiative indexes, explicit skips, and supersession history.
- Prepare architecture and design review summaries with human approval gates.

## Use Cases

- Define System Boundaries: Turn an accepted approach into component responsibilities, dependency rules, failure responses, and reviewable architecture.
- Coordinate Shared Interfaces: Define exact operations, types, errors, and ordering so independently assigned tasks can integrate against the same contract.
- Preserve Decision History: Record alternatives and reversal criteria, then supersede outdated decisions without deleting their original reasoning.

## Prompt Templates

### Draft an Architecture Overview

```
For [initiative], use the charter and accepted approach to draft the architecture overview. State constraints, component responsibilities, boundaries, and open questions. Stop for human review before recording approval.
```

### Record an Architecture Decision

```
For [initiative], document the decision about [topic]. Compare viable alternatives, accepted costs, reversibility, and observable reversal criteria. Link the decision to the architecture and prepare it for review.
```

### Define a Shared Interface

```
For [initiative], define the interface between [provider] and [consumer]. Specify exact operations, types, errors, ordering, concurrency, lifecycle, stability, and consumers. Identify missing information without inventing implementation details.
```

### Supersede a Frozen Contract

```
For [initiative], evaluate replacing [frozen interface] because [new evidence]. Draft its successor, affected consumer updates, decision rationale, and component design changes. Preserve prior document bodies and request approval before recording phase completion.
```

## Limitations

- Requires the sibling executor skill, its references, and helper scripts, which are not included in this package.
- Requires an existing initiative charter and an accepted approach or explicitly skipped discovery.
- Produces documentation and interface contract text, not implementation code or executed application tests.
- Helper safety is unverified, and the verification checklist conflicts with the stated approval sequence.

## Best Practices

- Provide the initiative charter, accepted approach, and measured constraints before drafting architecture.
- Review helper implementations and dependency paths before execution; keep validation read-only until explicit human approval.
- Keep contracts exact, index documents in the same change, and preserve superseded reasoning.

## Anti Patterns

- Starting specifications or recording passed phases before human approval.
- Letting separate tasks invent shared signatures, error contracts, or ordering rules.
- Editing historical decision bodies or frozen interfaces instead of writing linked successor documents.

## Security Audit

- Audited at: 2026-10-05T16:54:58.111\+00:00
- Summary: Most alerts are Markdown formatting, fixed sibling paths, or document identifiers rather than executable backticks, path traversal exploits, or reconnaissance. Required helper executions remain confirmed with low confidence because their implementations are outside the five reviewed files. Verification can record a passed phase before human approval; no evidence found of exfiltration, credential theft, or audit-directed prompt injection.

## Stats

- Views: 0
- Downloads: 0
- Favorites: 0
- Popularity score: 0