echo-flow
/echo-flow
Drive the whole echo SDLC loop from a single goal, auto-advancing clean stages and stopping only at the gates that matter. Use when the user wants to run or resume the full loop for a ticket.
- Author
- ybshankar010 ↗
- Repository
- echo ↗
- Licence
- Apache-2.0
- Last repository change
- 01.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 01.11.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Drive the whole echo SDLC loop from a single goal, auto-advancing clean stages and stopping only at the gates that matter. Use when the user wants to run or resume the full loop for a ticket.
Original author description
Drive the whole echo SDLC loop from a single goal, auto-advancing clean stages and stopping only at the gates that matter. Use when the user wants to run or resume the full loop for a ticket.
How it works
- Arguments
- Steps
- Under Codex
SKILL.md preview
---
name: echo-flow
description: Drive the whole echo SDLC loop from a single goal, auto-advancing clean stages and stopping only at the gates that matter. Use when the user wants to run or resume the full loop for a ticket.
---
# echo flow (Codex)
Codex port of echo's `/echo:flow` command. It drives the same loop through the stdlib
`bin/echo-*` CLIs (unchanged).
## Arguments
Skills have no structured arguments. Read the ticket id (`[A-Z]+-[0-9]+`) and any goal text
from what the user typed; never fabricate a ticket.
## Steps
This reduces the loop to a few touchpoints: run the mechanical work, auto-approve any stage
whose automated check comes back clean, and stop only where a human decision matters. It is
re-runnable: read `echo-stage status` and continue from wherever the item is.
### Setup
1. Extract a Jira ticket id (`[A-Z]+-[0-9]+`) from what the user typed. If none is present,
STOP and ask for it. Never fabricate one (organization policy).
2. Read `.echo/config.json`. The `autonomy` level decides which gates to stop at
(`gated` -> every stage; `checkpoint` (default) -> `plan` and `ship`; `auto` -> `ship`
and any failure). Do not decide this yourself; ask the bin
(`python3 bin/echo-stage gate-mode --stage <stage>`) per stage.
3. If research was requested, run the echo-research flow first so the intent can cite it.
4. If there is no active item yet (or it is a different ticket), run the echo-intent flow to
initialize and write `.echo/artifacts/<TICKET>/intent.md`.
### Drive loop
Repeat until the item reaches `done` or you hit a stop:
1. Run `python3 bin/echo-stage status` to see the current stage and gate.
2. If the current stage's artifact/action is not done yet, produce it with the matching
flow: spec -> echo-spec; plan -> echo-plan (with its critic maker-checker loop);
build -> echo-build (the builder + reviewer maker-checker loop); test -> echo-verify;
ship -> handled at the stop below.
3. Run the stage's automated check and read its result (intent/spec/plan use the critic,
build uses the reviewer, test uses the echo-verify exit code).
4. If the check FAILED (important/blocking findings, or verify non-zero): STOP. Summarize
what failed, do NOT approve, and say how to fix or override. A failed check always stops,
whatever the autonomy level.
5. Otherwise ask the bin whether to pause: `python3 bin/echo-stage gate-mode --stage <current-stage>`.
- `stop` -> summarize the artifact and the clean check result and STOP. Tell the user to
review and approve, and that re-running the flow resumes from here. At `ship`, once
approved, run the echo-ship flow, then run the mandatory post-ship watch if
`.echo/verify/<TICKET>-ci.md` does not exist yet
(`python3 bin/echo-watch run --ticket <TICKET>`).
- `auto` -> approve and advance without the user:
`python3 bin/echo-stage approve` then `python3 bin/echo-stage next`, then continue.
Under Claude Code this command also posts per-stage Jira progress comments through the
Atlassian MCP tools. That is Claude-only; skip it under Codex.
### On every stop
State plainly: the ticket, the stage you stopped at, why (a gate or a failure), what to
review, and how to resume. Do not auto-approve a stop gate, and do not weaken any check to
keep moving.
## Under Codex
Gates are advisory and orchestration is prose-driven. Where the Claude command spawns the
`critic`, `builder`, or `reviewer` via the Task tool, delegate in prose to the matching role
under `.codex/agents/`. See `.agents/skills/README.md` for the Known limitations before
relying on this.
Versions
The database has no other skills named echo-flow.
Database snapshot: 13.11.2026 · package version b02f8b2f5ce5 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100echo-next
Advance to the next SDLC stage and generate its artifact, blocking if the current gate is not approved. Use to move the loop forward after approving a stage. - 100echo
Echo framework guardrails, patterns, and best practices for AI-assisted development. Use when working with Echo projects, or when the user mentions Echo framework. Provides middleware patterns, routing, context handling, and REST API guidelines. - 100agentic-sdlc-loop
Runs a software ticket through the agentic SDLC loop with human gates. Ticket → intent + PRD (stop) → plan (stop) → branch, code, tests, PR (stop). Use when the user gives you a ticket, feature request, bug report or Monday/Jira item and wants it built spec-first, or says "run… - 100ticket-flow
Run a whole ticket end to end - understand, plan, build, test, docs, validate, review - with one writer in its own git worktree and every read-only stage in parallel, stopping only at human gates. Use for "work ticket PROJ-123", "do the whole ticket", "trabaja el ticket… - 100sdlc
Run the autonomous SDLC pipeline on a task — the single entrypoint driving spec → review → build → test → security → delivery through the profile's quality gates. Use to run the SDLC or ship a feature. - 100sdlc
Run the autonomous SDLC pipeline on a task — the single entrypoint driving spec → review → build → test → security → delivery through the profile's quality gates. Use to run the SDLC or ship a feature.