I'm excited to share SpecX, a task orchestration engine for teams using coding agents like Cursor and Claude.
## Motivation
While building projects with AI coding agents, I noticed a few patterns:
* As projects grew in size, writing effective prompts became progressively harder * Agents performed best when requirements were short and well-defined * Many everyday tasks — testing, deployment, documentation, reporting — were structured and repeatable, even across projects.
> The manual translation from goal to prompt felt redundant, lossy, and inefficient.
I decided to remove prompts from the equation entirely. Instead: * For automation, focus on the workflow and break it into steps. * For feature work, focus on requirements and break them into tasks.
## The Core Solution: Reliable Workflow Automation
At the center of SpecX is the Task Orchestration Engine.
You define Pipelines — reusable sequences of actions the agent must perform. Common use cases include:
* Automated compliance or audit checks * Reporting (code coverage, engineering velocity, documentation) * Refactor → test → verify loops
Built on top of the orchestration engine is the Requirement Tree, a structured, AI-assisted way to turn rough, unstructured ideas into well-defined tasks.
You write requirements the way you think; the engine builds them using one of the pipelines.
## Status
SpecX is in preview. I'd love feedback from the HN community — especially on the Pipeline model and the idea of separating goal definition from prompt generation.
* Login required (to protect your project context) * Requires a coding agent (Cursor or any MCP-enabled agent).
Try SpecX: https://redoxsoft.com Demo: https://www.youtube.com/watch?v=1JNYIhoHmbQ
Happy to answer questions about the architecture, design choices, or roadmap.