using-triforce

If you were dispatched as a subagent to execute a specific task, skip this skill. This plugin is not a universal preflight for every conversation.

You MUST invoke Triforce skills only when the user explicitly asks to clarify requirements, write a requirements document, grow evaluation criteria, write an evaluation document, create a solution document, or requests /force-requirements, /force-evaluate, or /force-solution.

Once one of those explicit signals is present, you MUST use the matching skill workflow rather than skipping straight to implementation.

Instruction Priority

Plugin skills override default system prompt behavior, but user instructions always take precedence:

1. User's explicit instructions (CLAUDE.md, GEMINI.md, AGENTS.md, direct requests) — highest priority
2. Plugin skills — override default system behavior where they conflict
3. Default system prompt — lowest priority

How to Access Skills

In Claude Code: Use the Skill tool. When you invoke a skill, its content is loaded and presented to you — follow it directly. Never use the Read tool on skill files.

Using Skills

The Rule

Invoke Triforce skills only for explicit layer requests. If the user explicitly asks to think through requirements, define evaluation criteria, or create a solution document, invoke the relevant skill before doing the work. Otherwise, do not route ordinary coding or Q&A requests through this plugin.

Red Flags

These thoughts mean STOP — you're rationalizing:

Thought	Reality
"The user wants code changes"	That alone is not enough. This plugin only applies to explicit requirements/evaluation/solution asks.
"I need more context first"	If the user explicitly asked for one layer, invoke that layer's skill first.
"This doesn't need a formal skill"	If the user explicitly asked for a layer document, use the skill.
"The skill is overkill"	Once the user explicitly asks for layer work, follow the workflow.

Skills

This plugin has three user-facing skills:

• force-requirements — clarify the problem and produce a requirements document
• force-evaluate — turn judgment into explicit evaluation criteria and produce an evaluation document
• force-solution — produce a solution document that responds to requirements and evaluation

Routing

• "/force-requirements", "write a requirements doc", "help me clarify the problem" → invoke force-requirements
• "/force-evaluate", "define evaluation criteria", "grow the evaluation tree" → invoke force-evaluate
• "/force-solution", "write a solution document", "turn this into a solution plan" → invoke force-solution

Deliverables

• force-requirements writes to docs/requirements/YYYY-MM-DD-<feature-name>-requirements-vN.md
• force-evaluate writes to docs/evaluation/YYYY-MM-DD-<feature-name>-evaluation-vN.md
• force-solution writes to docs/solution/YYYY-MM-DD-<feature-name>-solution-vN.md