From triforce
Use when the user explicitly asks to clarify a problem, think through requirements, or write a requirements document. Delivers a versioned requirements document.
How this skill is triggered — by the user, by Claude, or both
Slash command
/triforce:force-requirementsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Help turn a vague idea into a clear requirements document through collaborative dialogue.
Help turn a vague idea into a clear requirements document through collaborative dialogue.
HARD GATE: Do NOT write implementation code, scaffold a project, produce an evaluation document, or produce a solution document. Your only output is a requirements document.
Announce at start: "I'm using the force-requirements skill to clarify the problem and produce a requirements document."
Save documents to: docs/requirements/YYYY-MM-DD-<feature-name>-requirements-vN.md
CLAUDE.md, README.md, TODOS.md if they exist.docs/requirements/.Output: "Here's what I understand about the problem space and the relevant project context: ..."
Ask questions one at a time. Push vague answers until they become concrete.
Problem and user
Scope boundary
Constraints
Failure and edge cases
Success definition
Route based on complexity. Small changes may need only the first two questions.
Before writing the document, challenge the assumptions.
Present the resulting premises clearly and confirm them with the user if needed.
Save to docs/requirements/YYYY-MM-DD-<feature-name>-requirements-vN.md with this structure:
# [Feature Name] Requirements
## Background
Why this work exists. What problem it solves. Who feels the pain.
## Problem Statement
What is broken, missing, or unclear today.
## Requirements
### Functional Requirements
- FR-1: [requirement]
- FR-2: [requirement]
### Non-Functional Requirements
- NFR-1: [constraint or quality requirement]
## Scope Boundaries
What is explicitly in and out.
## Success Signals
How a human would know this solved the problem.
## Open Questions (resolved)
Questions raised and resolved during the process.
## Premises
Assumptions this version depends on.
After saving the document:
"Requirements document complete and saved to docs/requirements/<filename>.md. Please review it before moving on to evaluation or solution work."
npx claudepluginhub zhan7653/xutianding-marketplace --plugin triforceGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.