Workflows
Connect handoffs as the task requires.
The four skills have distinct responsibilities. When combining them, connect the work with precise requirements, candidate versions, and handoff files.
Start with the step that is missing now.
| Scenario | Suggested path |
|---|---|
| Advance one engineering task | Cohestra handles the stage currently needed |
| Execute several well-defined tasks | Cadra prepares and schedules; Cohestra executes engineering stages |
| Explore page visuals and implement them | Vistra explores, records the selection, and hands off the design before engineering |
| Review a period of work | Relatra verifies recorded outcomes, outstanding work, and resource usage |
If visual exploration is unnecessary, go directly to engineering task preparation. For a retrospective alone, use Relatra independently.
Every handoff has a purpose.
- Cohestra: requirements, design, implementation, review, fixes, and validation for one task.
- Cadra: task definitions, execution conditions, serial scheduling, and run recovery.
- Vistra: visual findings, candidates, selection rationale, and design handoffs.
- Relatra: outcome verification, outstanding work, and resource summaries for a period.
Choose status tools by purpose too. Cohestra's report gives a project task overview; Cadra's report summarizes a specified run; Relatra produces a period retrospective.
Take search history from requirements to retrospective.
This example includes visual exploration and an execution batch. Prepare all four skills, the project's Git workspace, host image capabilities, and the validation environment first.
Clarify requirements
Use Cohestra's need to define saving, deleting, clearing, and retaining search history after restart. Establish acceptance criteria.
Keep the returned task ID, original task directory, and requirements handoff path.
Explore visuals
Give Vistra the requirements handoff and existing search page. Explore static directions for the history area while preserving the brand and navigation.
Select and hand off
Review the candidates and explicitly adopt an exact version, or authorize a choice. Vistra then records the adoption scope, asset mapping, and unresolved decisions.
An explicit selection can proceed directly to handoff. Resolve missing key decisions or assets first when necessary.
Confirm the engineering design and register the same task
First invoke Cohestra's design interactively in the original task directory, with the requirements and Vistra's formal handoff, to settle the necessary engineering approach and open decisions. Existing confirmations remain valid. Then use Cadra's add with the original task ID and directory, explicitly binding the same target.
Register the requirements, engineering design, and visual handoff with the implementation flow; verify that code is the original task's legal next stage. Cadra dispatches only code, review, fix, and validate. Prepare need/design with human participation before admission.
Check and execute
Invoke ready and run separately. Once conditions pass, Cadra dispatches a worker and independent reviewer for this task, advancing implementation, independent review, necessary fixes and re-review, then validation serially as results require. New product or design decisions during execution block the task for preparation with human input.
Keep the returned run-id. Use report after completion. For interrupted execution, use resume to check the unfinished run first.
Review actual outcomes
Give Relatra the projects and period to verify deliverables, acceptance status, outstanding work, and observed usage.
For current progress, explicitly say “this week so far.” For visual work, provide exact handoff references and readable evidence.
Invoke these steps separately, continuing only after obtaining the preceding handoff. Resolve visual choices before the execution that depends on them.
Help later work find the exact basis.
Pass complete paths, task IDs, and candidate versions. When continuing an existing task, reuse its directory and state which decisions remain valid.
Resolve missing or uncertain materials first. A visual handoff informs engineering; engineering design still needs to check the implementation approach and validation methods. Do not enter Vistra modes as Cadra engineering stages.
The initial queue is ordered by priority and task ID, not by the order of a scope list. For new tasks during execution, use add, ready, then append to add the entire admitted batch at the end; sort only within the new batch. Complete upstream dependencies before checking downstream readiness, then append to a still-running run or establish a subsequent run.
Relatra does not currently collect Vistra directories automatically. Even with artifact references, actual delivery needs confirmation through readable evidence.
Choose a path. Prepare its inputs.
Start with the scenario that best matches your goal. Combine only the skills it actually needs.