implement

Describe the task in plain words, such as "implement the next task from project X". The skill reads tasks.md, picks the first unchecked task whose dependencies are done, writes tests from its acceptance criteria, implements it, and marks it done on MySpec.

Each EARS+ criterion maps to a test structure: WHEN/THEN becomes arrange-act-assert, IF conditions become error-path tests, and NFR targets become measurable checks. Tests are named with the requirement id, like FR-003 AC2, for traceability.

Yes. It supports greenfield bundles (constitution, requirements, solution, tasks), MySpec brownfield deltas with AR/BR/CR requirement ids, and OpenSpec changes under openspec/changes/<id>/. Brownfield work matches the existing codebase architecture.

Writes use optimistic concurrency: update_spec_file requires an expected_version token from the last read. On conflict, the skill re-reads the file, re-applies only its own change, and retries, so nobody's work is overwritten.

The myspec MCP server requires a MySpec login or API token. When tools are missing or return authentication errors, the skill stops and directs you to the setup skill to sign in or set MYSPEC_API_TOKEN.

Yes, but only tasks with met dependencies and disjoint files may be delegated to parallel subagents. The default is sequential, and only the parent session writes tasks.md and progress.md updates.