ferrox-quick

Execute small ad hoc tasks with atomic commits and state tracking.

21|9|Updated Jul 21, 2026
One-click install
npx skills add https://github.com/FerroxLabs/ferrox-factory --skill ferrox-quick
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ferrox-quick
Source: https://github.com/FerroxLabs/ferrox-factory/tree/main/skills/ferrox-quick
Command: npx skills add https://github.com/FerroxLabs/ferrox-factory --skill ferrox-quick

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you complete small, ad-hoc work without losing the safety and traceability guarantees of the Ferrox system. It removes the overhead of full planning while still keeping atomic commits, task state tracking, and resumable execution.

Core Features & Use Cases

  • Quick task execution: Handles small fixes, cleanup work, and short implementation tasks through a streamlined workflow.
  • Task lifecycle management: Supports listing, checking status, and resuming quick tasks stored in .planning/quick/.
  • Quality controls on demand: Can add discussion, research, validation, and verification when a task needs more rigor.
  • Use case: Use this Skill when you already know the change you want and need it completed quickly with Ferrox-style discipline.

Quick Start

Ask the agent to run a quick Ferrox task for your change request and include any flags such as discuss, research, or validate if you want extra checks.

Frequently Asked Questions about ferrox-quick

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I execute small ad hoc tasks with atomic commits in a workflow?

To execute small ad hoc tasks with atomic commits, you can use a streamlined workflow that processes quick fixes and status checks while maintaining persistent state tracking. This allows rapid implementation without full planning ceremony.

What is the best way to resume in-progress work without losing traceability?

The best way to resume in-progress work without losing traceability is to use a workflow that stores task states in a dedicated quick task directory. This enables resumable execution and persistent state tracking for interrupted fixes.

How do I add validation and research checks to quick task automation?

You can add validation and research checks to quick task automation by passing optional flags during subcommand parsing. This injects discussion, research, validation, and verification gates when a task requires more rigor.

Does task automation work with state tracking for resumable execution?

Yes, task automation works with state tracking for resumable execution by managing task lifecycles in a specific directory. It supports listing, checking status, and resuming tasks to ensure atomic commits are preserved.

When should I avoid using a quick task workflow for software engineering?

You should avoid using a quick task workflow when your software engineering change requires full planning ceremony, complex architecture decisions, or extensive research that exceeds the scope of small ad hoc fixes and cleanup work.