dtash-guidance

cc-guidance

A Claude Code plugin for teaching the agent persistent, project- or user-level rules — and keeping the rule set internally consistent as it grows.

What's in the box

• /guidance — the workflow you invoke when you want to teach the agent a new rule, change one, or remove one.
• Capability skills — the storage format the workflow writes into. Each capability is a focused, self-describing skill that the agent adopts when its description matches the task at hand.

The /guidance workflow

Invoke /dtash-guidance:guidance whenever you correct the agent's approach and want the lesson to persist. The skill will:

1. Restate the rule — name the triggering situation concretely ("writing Python tests"), not as a topic ("code quality").
2. Find the right home — update an existing capability, create a new one, or split if the concern differs. Defaults to project scope; say "user scope" to override.
3. Check for contradictions with overlapping rules and resolve before writing.
4. Write the rule with a rationale and good/bad examples.
5. Audit nearby examples so they still comply with the new rule.
6. Refine the capability's description so future sessions actually adopt it.
7. Propagate to subagents by adding the capability to their skills: frontmatter so delegated work picks it up too.
8. Retroactively fix work in the current session that violates the new rule.
9. Confirm what changed and where.

Why this shape

• Rationale-first. Every rule carries the why, so future-you (or the agent) can judge edge cases instead of following the letter blindly.
• One concern per capability. Granular skills compose cleanly for complex tasks; broad ones either fail to trigger or overreach silently.
• Descriptions decide everything. Adoption is description-driven — a vague or topic-shaped description means the rule never fires. The workflow treats description writing as the highest-leverage step.
• Subagent propagation is explicit. Subagents don't perform capability selection; rules reach them only via the skills: field or inlined prompts. Step 7 makes wiring this a routine, not an afterthought.

Capability skills

A capability skill is a regular skill with type: capability in its frontmatter. Two conventions matter:

• Name. Directory and name: start with capability- (e.g., capability-python-style) so capabilities are visually distinct from workflow skills.
• Description. Names a concrete triggering situation and enumerates the modes it applies in — planning, Q&A, design, review, writing. The agent adopts a capability by reading this field, so it's load-bearing.

capability-sub-agent ships with the plugin and codifies how to wire capabilities into delegated work.

Install

/plugin marketplace add Wopple/cc-guidance
/plugin install dtash-guidance@cc-guidance

Then invoke with /dtash-guidance:guidance.