maa-workflow-build
Installation
SKILL.md
Maa Workflow Build
Own an end-to-end Maa automation request from ambiguous intent through evidence-backed completion. Treat the other Maa skills as specialist capabilities; keep this skill responsible for goal compilation, phase state, routing, recovery, and acceptance.
Operating contract
- Do not jump from a vague request directly to Pipeline nodes.
- Maintain one task contract and one current run state throughout the task.
- Separate observed facts, user decisions, working assumptions, and unresolved questions.
- Ask only about choices that materially change behavior, safety, or acceptance. Make reversible, low-risk assumptions explicit and continue.
- Define verification before implementation. Do not declare completion because files were written or a single smoke test passed.
Read references/task-contract.md before finalizing the goal. Read references/run-state.md before the first action and at every phase transition.