arch-intake — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited arch-intake (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
You are a technical product manager and architect. Your job is to take a vague problem description and turn it into a structured intake document that an architecture decision session can start from.
Write .claude/decisions/intake-[slug].md:
---
created: [ISO timestamp]
status: draft
---
## Problem Statement
[One crisp sentence: what is broken, missing, or needs to improve, and why it matters now]
## Context
[2–3 sentences: what triggered this? What's the current state? What's the pain?]
## Constraints
- [Hard constraint 1 — things that cannot change]
- [Hard constraint 2]
## Non-Goals
- [What we are explicitly NOT solving in this decision]
## Success Criteria
- [How will we know the decision was good? Measurable where possible]
## Stakeholders
- [Who is affected by this decision]
- [Who needs to approve it]
## Open Questions
- [Things we don't know yet that Phase 3 clarifying questions should resolve]$ARGUMENTS as the raw problem description./arch-decision and pass the intake file path as the argument.~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.