Audience and Scope Discipline
Protect the intended audience, authorized scope, privacy boundary, and established structure of an artifact.
Use when: Protect the audience, scope, privacy boundary, and established structure of product-facing or derived artifacts when implementation or content could drift.
Install only this skill
Section titled “Install only this skill”arcantry skills link audience-scope-discipline --scope userThis links only audience-scope-discipline to the standard user location, ~/.agents/skills. Use --scope repo for one repository, or add --compat claude when that optional alias is needed.
What it helps with
Section titled “What it helps with”- Distinguish implementation inputs from information the intended reader actually needs.
- Preserve exact evidence and recovery details only when an established audience task requires them.
History
Section titled “History”- 2026-10-03 - Keep requirements out of reader-facing copy by default: Audience guidance now admits a visible detail only when the request, established audience or current reader task requires it, with focused examples for preserving exact evidence and actionable recovery without exposing unrelated implementation data.
- 2026-08-18 - Preserve derived artifact fidelity: Audience and scope guidance now preserves the structure and comparison semantics of existing artifacts unless the requester explicitly authorizes a different representation.
- 2026-08-18 - Coordinate project knowledge and agent workflows with Arcantry: Arcantry provides local-first project configuration, safe repository adoption, a portable catalog of focused agent skills, and one documented workflow for maintaining project intent, release meaning, task intake, verification, and audience-safe content.
- 2026-08-17 - Unified Arcantry capabilities: Arcantry now combines its OpenSpec lifecycle with reusable skills, a complete Codex plugin, a versioned catalog, and one CLI for safe repository adoption and skill management.
Examples
Section titled “Examples”Turn requirements into audience-fit output
Section titled “Turn requirements into audience-fit output”Prompt
Use the audience-scope-discipline skill to turn these requirements into reader-facing content without exposing every available field.
Expected outcome
Only details admitted by the reader’s current task become visible, while required exact evidence remains usable.
Guard a narrow implementation
Section titled “Guard a narrow implementation”Prompt
Apply the audience-scope-discipline skill while implementing this request. Do not absorb adjacent cleanup or local setup into the product.
Expected outcome
The smallest coherent change, with material risks challenged once and unrelated improvements left separate.