upwork-workflows

Use when working with `.c4`/`.likec4` files or LikeC4 CLI/config questions where exact DSL/CLI syntax is required, especially for strict command/snippet-first…

Autonomously implement, fix or refactor software toward a spec, with property-based tests as the fitness function (Karpathy autoresearch loop).

Creates clear, specific Upwork job posts and guides clients through drafting, publishing, updating, and closing them.

Researches an Upwork job and a freelancer's real experience to create a tailored, honest proposal and guide its review and submission.

Guides an Upwork client from candidates to a signed contract by searching for freelancers, reviewing proposals, shortlisting, inviting, and preparing offers.

Find deepening opportunities via CONTEXT.md and docs/adr/.

Discipline for a build worker that edits code under a lead's brief -- smallest diff, own tools, runs VERIFY itself, stops rather than guesses.

Simplify and refine recently modified code for clarity, consistency and maintainability while preserving all functionality.

Routes an ask to a playbook, then leads it: feature, bugfix, testing, review, ship, babysit, pickup, pause, cleanup, ice, qa, refactor, perf.

Use on /debug-mantra and whenever debugging starts: a bug report, something broken, throwing or failing, a request to diagnose, a pasted stack trace.

Create or wire project automations: reusable scripts, build scripts, custom tasks, or ACP-discoverable automations.

Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in.