Arch intake

Skill jsingh6/arch-decision/skills/arch-intake

Open-source ADR orchestrator — explores your codebase, proposes approaches, writes Architecture Decision Records automatically

Install

npx -y skills add jsingh6/arch-decision --skill arch-intake

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Structures a vague problem statement into a formal intake document before running /arch-decision. Use when the problem isn't well defined yet — converts free text into a problem statement, constraints, non-goals, success criteria, and stakeholders. Output feeds directly into /arch-decision Phase 1.

SKILL.md

1.9 KB, 357 tokens by cl100k_base, as published. Nobody here has run it

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.

What you produce

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]

How to run

Parse $ARGUMENTS as the raw problem description.
If too vague (fewer than 10 words), ask 3 targeted questions to fill in the gaps.
Draft the intake doc and show it to the user.
Ask: "Does this capture the problem correctly? (A) Yes — run /arch-decision now (B) Edit something first"
On (A): tell the user to run /arch-decision and pass the intake file path as the argument.
On (B): make edits and re-confirm.