From art-project
Concept Brief with epistemic fields (proposition / anti-proposition / disconfirmation condition / Frayling-type declaration). Stay-rough default — prose stays in the artist's voice. No auto-completion of gaps.
How this command is triggered — by the user, by Claude, or both
Slash command
/art-project:briefsonnetThe summary Claude sees in its command listing — used to decide when to auto-load this command
Invoke the `art-ideation` skill in **brief** mode. Produce a Concept Brief with the v0.2 epistemic schema. The Brief is **not** a marketing one-pager; it is a *proposition document* in the Journal for Artistic Research / Research Catalogue exposition tradition. **Required fields (in order):** 1. **Working title** — artist's preferred title; provisional is fine. 2. **Provocation** — the research question implicit in the impulse (Borgdorff 2011, 2012, C4). What does the work want to find out? What can only be found out by making it? 3. **Proposition** — the claim the work proposes. What do...
Invoke the art-ideation skill in brief mode.
Produce a Concept Brief with the v0.2 epistemic schema. The Brief is not a marketing one-pager; it is a proposition document in the Journal for Artistic Research / Research Catalogue exposition tradition.
Required fields (in order):
IRON RULE — stay-rough default. Prose stays in the artist's voice. Your job is to force articulation of each field, not to smooth the prose. Default behavior: ask the artist to dictate the proposition / anti-proposition / disconfirmation / etc. and capture the wording with minimal edit. Preserve grammatical quirks, mid-sentence stops, contradictory clauses. A --polish flag exists for ESL or grammar pass, but is not the default.
The reason for stay-rough: AI-detectable smoothness is itself a reject signal at real review venues (curators, grant committees, residencies have learned to spot LLM-polished applications). Keeping the artist's voice — including its roughness — is the v0.2 mitigation against ghost-writer-effect harm.
IRON RULE — no auto-completion of gaps. If the artist cannot articulate the disconfirmation condition or the anti-proposition, report the gap rather than filling it. Format the empty field as:
**Condition for disconfirmation:** *[artist did not articulate; gap acknowledged
per Borgdorff criticisability discipline — return to this field before submission]*
Plausible-sounding filler in these fields is a failure mode, not a success. Empty + acknowledged > filled + fabricated.
IRON RULE — mandatory AI-assistance disclosure footer. Every Concept Brief output ends with a verbatim footer:
---
> *Drafted with AI articulation support via the **art-project** Claude Code plugin (https://github.com/joonhyungbae/art-project, CC-BY-NC 4.0). The plugin enforced the 10-field schema and the stay-rough discipline; voice, propositions, and refusals are the artist's. Authentic Practice Boundaries: ideation happens in the studio, not the chat; this Brief is the propositional articulation for it.*
The artist can remove this footer before submitting to a venue whose AI-disclosure policy differs, but the default is for the Brief to be self-disclosing — addressing harm class 4 (Authorship-perception shift; Wordcraft / Sparks / ghostwriter literature) at the artefact-level rather than relying on the artist to remember.
See art-ideation/SKILL.md for the full mode specification.
npx claudepluginhub joonhyungbae/art-project --plugin art-project/briefGenerates a creative brief for a marketing campaign after interactively collecting scope, type, deliverables, and timeline preferences.
/briefGenerates a concise visual briefing on project state, progress, key decisions, blockers, and next steps from git status, specs, tasks, and context.
/briefConducts interactive dialog to elicit product details, then writes concise brief (vision, problem, users, success) to docs/product-brief.md.
/briefGenerates contextual legal briefings for teams: daily summaries of urgent items and deadlines, topic research, or incident responses from connected email, calendar, chat, CLM, and CRM sources.