clarifier

Clarify system state with artifact-based, non-directive explanations.

Updated Feb 10, 2026

Search Tags:#governance #artifacts #system-state #explainability #legibility #clarifier

Ready to run

npx skills add https://github.com/Will-Aveva/phoenix-chassis --skill clarifier

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: clarifier
Source: https://github.com/Will-Aveva/phoenix-chassis/tree/main/.agent/skills/clarifier
Command: npx skills add https://github.com/Will-Aveva/phoenix-chassis --skill clarifier

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Legibility of system state is often poor, leading to ambiguity and misinterpretation. The CLARIFIER role provides anchored, artifact-based explanations to make complex states understandable without directing action or governance.

Core Features & Use Cases

Artifact-backed explanations: every interpretation references concrete artifacts, sources, and authority structures.
Non-directive guidance: clarifications orient users and stakeholders without altering system behavior or governance decisions.
Audit-friendly outputs: structured summaries that support traceability and reviews.

Quick Start

Provide an artifact-backed, clearly labeled explanation of the current system state in plain language.

Frequently Asked Questions about clarifier

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I make complex system state legible for governance reviews?▼

Make system state legible by anchoring explanations to concrete artifacts and the established authority chain. This provides artifact-backed interpretations that orient stakeholders without directing action or altering governance decisions.

What is artifact-based explainability for system state?▼

Artifact-based explainability renders system state understandable by referencing concrete artifacts, sources, and authority structures. It produces audit-friendly summaries that support traceability and reviews without unilateral actions.

How do I clarify system state without triggering unilateral actions?▼

Clarify system state without unilateral actions by applying non-directive guidance to exploratory tasks. This ensures artifacts guide interpretation and orient users while conforming to the clarify phase schema and avoiding behavioral changes.

When do I need to anchor explanations to artifacts and authority chains?▼

Anchor explanations to artifacts and authority chains when legibility is poor and understanding is required but direction is not given. This approach resolves ambiguity and misinterpretation in governance-oriented or exploratory tasks.

Does clarifying system state require predefined direction or governance inputs?▼

Clarifying system state does not require predefined direction. It is designed for exploratory or governance-oriented tasks where understanding is needed, using available artifacts and constraints to guide interpretation independently.

What is the best way to structure audit-friendly summaries of system state?▼

Structure audit-friendly summaries by conforming to the clarify phase schema. Reference available artifacts and constraints to produce structured, traceable outputs that clearly explain the current system state in plain language.