How do I install the Ferrox Spec Phase skill?

Run npx skillmds@latest add ferroxlabs/ferrox-spec-phase in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Ferrox Spec Phase skill do?

You want WHAT a step delivers pinned down, with ambiguity scored, before discussing how It is listed under Coding & Dev Tools on SkillMD.

Is Ferrox Spec Phase safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Ferrox Spec Phase?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Ferrox Spec Phase free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Ferrox Spec Phase?

FerroxLabs (@ferroxlabs) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Ferrox Spec Phase by ferroxlabs — Agent Skill

Name: Ferrox Spec Phase
Author: FerroxLabs

File contents

Position in workflow: spec-phase → discuss-phase → plan-phase → execute-phase → verify

How it works:

Load phase context (PROJECT.md, REQUIREMENTS.md, ROADMAP.md, STATE.md)
Scout the codebase — understand current state before asking questions
Run Socratic interview loop (up to 6 rounds, rotating perspectives)
Score ambiguity across 4 weighted dimensions after each round
Gate: ambiguity ≤ 0.20 AND all dimensions meet minimums → write SPEC.md
Commit SPEC.md — discuss-phase picks it up automatically on next run

Output: {phase_dir}/{padded_phase}-SPEC.md — falsifiable requirements that lock "what/why" before discuss-phase handles "how"

Flags:

--auto — Skip interactive questions; Claude selects recommended defaults and writes SPEC.md
--text — Use plain-text numbered lists instead of TUI menus (required for /rc remote sessions)

Context files are resolved in-workflow using init phase-op.

MANDATORY: Read the workflow file BEFORE taking any action. The workflow contains the complete step-by-step process including the Socratic interview loop, ambiguity scoring gate, and SPEC.md generation. Do not improvise from the objective summary above.

---name: ferrox-spec-phasedescription: You want WHAT a step delivers pinned down, with ambiguity scored, before discussing how---<objective>Clarify phase requirements through structured Socratic questioning with quantitative ambiguity scoring.**Position in workflow:** `spec-phase → discuss-phase → plan-phase → execute-phase → verify`**How it works:**1. Load phase context (PROJECT.md, REQUIREMENTS.md, ROADMAP.md, STATE.md)2. Scout the codebase — understand current state before asking questions3. Run Socratic interview loop (up to 6 rounds, rotating perspectives)4. Score ambiguity across 4 weighted dimensions after each round5. Gate: ambiguity ≤ 0.20 AND all dimensions meet minimums → write SPEC.md6. Commit SPEC.md — discuss-phase picks it up automatically on next run**Output:** `{phase_dir}/{padded_phase}-SPEC.md` — falsifiable requirements that lock "what/why" before discuss-phase handles "how"</objective><execution_context>@~/.claude/ferrox-core/workflows/spec-phase.md@~/.claude/ferrox-core/templates/spec.md</execution_context><runtime_note>**Copilot (VS Code):** Use `vscode_askquestions` wherever this workflow calls `AskUserQuestion`. They are equivalent.</runtime_note><context>Phase number: $ARGUMENTS (required)**Flags:**- `--auto` — Skip interactive questions; Claude selects recommended defaults and writes SPEC.md- `--text` — Use plain-text numbered lists instead of TUI menus (required for `/rc` remote sessions)Context files are resolved in-workflow using `init phase-op`.</context><process>Execute end-to-end.**MANDATORY:** Read the workflow file BEFORE taking any action. The workflow contains the complete step-by-step process including the Socratic interview loop, ambiguity scoring gate, and SPEC.md generation. Do not improvise from the objective summary above.</process><success_criteria>- Codebase scouted for current state before questioning begins- All 4 ambiguity dimensions scored after each interview round- Gate passed: ambiguity ≤ 0.20 AND all dimension minimums met- SPEC.md written with falsifiable requirements, explicit boundaries, and acceptance criteria- SPEC.md committed atomically- User knows they can now run /ferrox-discuss-phase which will load SPEC.md automatically</success_criteria>

Frequently asked questions

Ferrox Spec Phase