FerroxLabs/ferrox-factory - Page 2

ferrox-phase

You want to add, insert, remove or edit steps in the roadmap itself. Expert level surgery

ferrox-plan-phase

Ready to work out the next step in detail before building it. Produces a plan to execute

ferrox-plan-review-convergence

Replan against cross-AI review until the concerns are actually resolved, not just noted

ferrox-pr-branch

You want a PR branch without the .planning/ commits, so reviewers see only real code

ferrox-profile-user

You want Ferrox to learn how you work and adapt its questions and defaults to you

ferrox-progress

Where am I, what is next, or just say what you want. The unified situational command

ferrox-quick

A small self contained task, with atomic commits and state tracking but no planning ceremony

ferrox-resume-work

Coming back to work you left part way through. Restores the full context you had

ferrox-review-backlog

You have parked items and want to decide which ones join the current milestone

ferrox-review

You want other AI models to critique a plan before you build it. Cross-AI peer review

ferrox-secure-phase

You want to confirm a finished step's threats were actually mitigated in the code

ferrox-settings

You want to change workflow toggles and which models Ferrox uses

ferrox-ship

A step works and you want it to leave your machine. Opens a PR once verification passes

ferrox-sketch

You want to see what it could look like before building it. Throwaway HTML mockups

ferrox-spec-phase

You want WHAT a step delivers pinned down, with ambiguity scored, before discussing how

ferrox-spike

You want to find out whether something will work at all. Throwaway experiment, not a build

ferrox-stats

You want the numbers on this project. Steps, plans, requirements, git activity, timeline

ferrox-surface

Too many commands, or too few. Applies a profile or disables a cluster without reinstalling

ferrox-thread

You want a named context thread that survives across sessions for one line of work

ferrox-ui-phase

A step involves frontend work and you want the design pinned down before it is built

ferrox-ui-review

Frontend work is built and you want it audited on look, layout and accessibility

ferrox-ultraplan-phase

[BETA] You want planning offloaded to the ultraplan cloud, reviewed in a browser, imported

ferrox-undo

You want the last step put back the way it was. Reverses its commits safely, in order

ferrox-update

You want the latest Ferrox, with the changelog shown before anything changes

ferrox-validate-phase

You suspect a finished step has coverage gaps. Audits and fills Nyquist validation gaps

ferrox-verify-work

Something was built and you want to confirm it works, by trying it rather than trusting it

ferrox-workspace

You want isolated environments to work in. Create, list or remove Ferrox workspaces

ferrox-workstreams

You want independent tracks of work running side by side. List, create, switch, resume

ferrox-frontend-design

Use when building or restyling any frontend or UI surface - web pages, components, dashboards, landing pages, HTML mockups, or visual companion screens. Covers aesthetic direction, typography, layout, copy, the anti-template discipline, the design knowledge…

ferrox-using-skills

Use when starting any conversation: invoke the relevant Ferrox discipline or lifecycle workflow skill before acting, including before clarifying questions.

ferrox-ns-context

codebase intel | map graphify docs learnings mempalace

ferrox-ns-ideate

exploration capture | explore sketch spike spec capture

ferrox-ns-manage

config workspace | workstreams thread update ship inbox

ferrox-ns-project

project lifecycle | milestones audits summary

ferrox-ns-review

quality gates | code review debug audit security eval ui

ferrox-ns-workflow

workflow | discuss plan execute verify phase progress

ferrox-receiving-code-review

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

ferrox-requesting-code-review

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

ferrox-systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

ferrox-test-driven-development

Use when implementing any feature or bugfix, before writing implementation code