Player profile
Ordewell
An Apache-2.0 terminal CLI and TUI that turns one goal into an ordered, editable plan of coding-agent tasks, each pinned to its own runner, model, mode, and effort, where a task counts as done only when its own completion marker appears in that runner's output.
Profile
Where it fits
Ordewell is an Apache-2.0 command-line tool and terminal UI for coding-agent work that starts from a goal instead of a prompt. A planner session that is refused edit commands inspects the repository and returns a structured plan of tasks with explicit dependencies, each pinned to a runner, model, mode, and effort level, and the operator can edit, retarget, reorder, or remove tasks before anything executes.
It belongs in Parallel Coding-Agent Runners because the plan, not a chat session, is what the runtime schedules: once a task's dependencies are satisfied it runs alongside its siblings on the harness the operator assigned to it, so Claude Code, Codex, and OpenCode can each carry different parts of one goal. Each task decides it is finished by emitting its own unique completion marker into its runner output, which is what the graph records as the verdict. Tasks share the repository working tree, so the plan separates them by dependency and file scope rather than by a checkout per task.
Builder web analytics
Measure projects built with Ordewell
Ordewell plans a goal into ordered tasks and runs each one on the harness the operator assigns. Agent Analytics supplies measured user behavior on the surfaces those runs change.
Point Agent Analytics at the deployed surface Ordewell tasks change. Agent Analytics measures events on the deployed surface after deployment; it does not replace Ordewell's plan graph, task output, or completion markers.
First loop to measure
- a goal is planned into tasks that build or revise a site, docs path, onboarding flow, or app surface
- the reviewed changes are merged and deployed
- the deployed surface reports visits, sources, CTA clicks, signup, activation, and funnel events to Agent Analytics
- a later plan, or the operator, reads those outcomes and scopes the next set of tasks from measured user behavior
Copyable prompt
Use Agent Analytics for this project. If event reporting is missing, add the tracker and report events for this project surface, including page, traffic source, CTA click, signup, activation event, funnel step, or shipped task. Verify events are arriving. Then fetch the last 7 days and compare them with the prior 7 days. Tell me which page, traffic source, CTA click, signup, activation event, funnel step, or shipped task moved users toward value, where users dropped off, which sources mattered, and what my agent workflow should improve next.