implement
implement - Implementation Stage
Invariants
- Require an approved task document before changing implementation files.
- Treat the task document as the primary scope contract.
- Do not broaden scope without user approval.
- Do not rely on provider-specific model switch commands.
implement autois the only automation entry point.
Runtime adapters may expose this stage as a slash command, menu action, or natural-language skill invocation. The portable stage name is implement.
Argument Handling
{ID}or{task-name}identifies the task document.autoenables the implementation-to-ship automation chain after implementation.--tier fast|balanced|deepmay override the task document recommendation only if the active runtime supports tier routing.
If a user asks for provider-specific model names, treat them as adapter-level preferences rather than core workflow semantics.
More from eljun/workflow-skills
document
Use this skill after verification passes and the user approves the result. Updates feature docs, user guides, task retrospectives, LEARNINGS.md, and durable project instructions when the completed task changes reusable workflow knowledge.
43task
Use this skill when the user wants to plan a new feature, bug fix, enhancement, documentation update, or chore before implementation. Creates or updates a reviewed task document in docs/task/ and updates TASKS.md, then stops for human approval.
42test
Use this skill after implementation passes the quality gate and the user wants verification. Runs capability-based checks from the task document, including unit, integration, browser, API, CLI, CI, or manual checks, and writes docs/testing/*.md.
42simplify
Use this skill after implementation and before testing to run a quality gate. Reviews changed files against the task document, checks maintainability standards, classifies plan deviations, and decides whether the work can proceed to verification.
41ship
Use this skill after documentation is complete and the task is approved. Runs pre-ship checks, prepares a branch or pull request, updates TASKS.md, and leaves release timing to the release stage.
40release
Use this skill when one or more ready-to-ship tasks have been merged and the user wants a versioned release. Generates changelog entries, creates tags or release notes, and moves merged tasks to Shipped.
39