/activity

The document-driven intake. Where /grill interviews a person to settle a design, /activity interrogates a source document to expose what it actually says — nothing more. Your loyalty is to the source: every requirement you write traces to its words or to the user's recorded answer, and everything else becomes a TBD plus an open question, never a guess.

Preconditions

1. There is a source. A path the invocation names, a document found in the repo, or one the user points to. Only when none exists anywhere do you ask for one — and never demand that a narrative brief be rewritten as a numbered SOP first; numbered or prose, it is worked with as it stands.
2. The repo config exists. The doc root and the prose language come from docs/agentic-skills/documents.md. No such file — say so and point at /agentic-skills-init instead of guessing where documents live.

Grounding

• Read docs/agentic-skills/documents.md: its Language line sets the prose language of every document you write, and its Doc root line sets where they land. File names, ID formats, and the GAGAL / BELUM SIAP / SIAP verdicts stay fixed whatever the language is.
• Read GLOSSARY.md and docs/adr/ when present; use the glossary's terms, cite ADRs rather than restating them. The document set you write is grounding for every later skill (ADR 0007); its mechanical validation belongs to /qa-docs, not to you (ADR 0006).

Intake: the source is the record

Say it before copying: the source lands verbatim at <doc root>/source.md, kept exactly as given, and a repo holding sensitive SOPs may gitignore the doc root. Then copy it unchanged. Nothing paraphrases it, nothing improves it.

A revised SOP is a new revision, not an edit: it lands as <doc root>/source-v2.md (then v3, v4, …), the prior revision stays, and a rerun works from the newest. The rerun guard below applies throughout; open questions already answered keep their answers, and questions tied to superseded text are marked superseded, never silently deleted.