spec-arch-author

Files (1)

• SKILL.md

SKILL.md (first lines)

# Spec ARCH author

Playbook: `SPECFORGE_HOME/ENGINEERING-PLAYBOOK.md`

## Gate
Do not start unless linked `REQ-NNN.md` has `Status: APPROVED`.

## Deliverables
1. `.specs/architecture/ARCH-NNN-slug.md`
2. `.specs/decisions/ADR-NNN-slug.md` for each significant decision (append-only; supersede with new ADR)
3. Update `.specs/contracts/api/openapi.yaml`, `contracts/data/models.md`, `contracts/events/schema.md` when contracts change

## ARCH template

```markdown
# ARCH-NNN — [Feature Name]
> Status: DRAFT | APPROVED
> Reads: REQ-NNN | Date: YYYY-MM-DD

## Approach

## Alternatives considered
| Option | Pros | Cons | Decision |

## Component design

## API / data changes

## Failure modes

## Security surface

## Infra / ops impact

## Objections resolved
```

## ADR template

```markdown
# ADR-NNN — [Title]
> Date: YYYY-MM-DD | Status: DRAFT | APPROVED | Supersedes: —

## Context
## Decision
## Consequences
## Alternatives rejected
```

## Rules
- ≥2 alternatives per major decision in the ARCH table.
- Do not write application code in this skill—specs only.
- Keep ARCH `Status: DRAFT` until the **user** sets `APPROVED`.
- After challenger: resolve objection IDs in **Objections resolved**; HANDOFF `READY_FOR_APPROVAL` and **stop** — do not self-approve.

End with skill `spec-handoff`.

From sushilti80/specforge-engineering-team, MIT.

More from sushilti80/specforge-engineering-team