A guided workflow for implementing a ticket from analysis through review and reporting. It requires reading the project's rules, proposing a plan, documenting the change, writing the code, verifying it, and saving an implementation report.

Use it for backend ticket implementation, especially when the task needs a plan, updated specifications, linting, tests, and a final report.

It prevents coding from starting before the work is understood and approved, and ensures the finished change has documented verification. It also keeps implementation work consistent across tickets.

How systemowiec/ai-agents-workspace-starter configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to systemowiec/ai-agents-workspace-starter. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/systemowiec/ai-agents-workspace-starter/main/.claude/commands/implement.md

Clone the repo

git clone --depth 1 https://github.com/systemowiec/ai-agents-workspace-starter

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/systemowiec/ai-agents-workspace-starter/implement/github.svg)](https://agentmods.dev/commands/systemowiec/ai-agents-workspace-starter/implement)

Your own site

<a href="https://agentmods.dev/commands/systemowiec/ai-agents-workspace-starter/implement"><img src="https://agentmods.dev/badge/commands/systemowiec/ai-agents-workspace-starter/implement/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/systemowiec/ai-agents-workspace-starter/implement"><img src="https://agentmods.dev/badge/commands/systemowiec/ai-agents-workspace-starter/implement.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 6 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 198 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00006	$0.00198
Opus 5.5	$0.00002	$0.00079
Sonnet 5.5	$0.00001	$0.00040
Haiku 4.5	$0.00001	$0.00020

Measured 2mo ago against content hash fa3a02aca3e6, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

implement scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/commands/implement.md · 24 lines

What it actually says

Steps

Read .agents/roles/backend-engineer.md - Your role
Read .agents/workflows/spec-development.md - MANDATORY flow
Read appropriate skills from .agents/skills/
Read .agents/learnings/gotchas.md - known gotchas
Read AGENTS.md - global rules

Workflow

Analyze the task
Propose a PLAN (files to change, modules, risks)
Wait for plan approval
Update documentation BEFORE code (Documentation First)
Implement
Run verification: .agents/workflows/post-impl-verify.md
Run: make lint && make test
Save report in docs/specs/{layer}/{PREFIX}-NNN/impl-backend-engineer.md
Inform user: "Implementation complete. Report ready for review."

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 24 lines · 6 tokens per session scan A fa3a02aca3e6

Subscribe to this mod's changes

implement is a command published in the GitHub repository systemowiec/ai-agents-workspace-starter (2 stars, last pushed 7mo ago), licensed MIT. It adds 6 tokens to every session and 198 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Planning Project management

implement next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
implementsystemowiec/ai-agents-workspace-starter	Command	2	7mo ago	MIT	A	6	Claude Code
checklistgithub/spec-kit	Command	148k	today	MIT	A	13	Claude Code
clarifygithub/spec-kit	Command	148k	today	MIT	A	27	Claude Code
specifygithub/spec-kit	Command	148k	today	MIT	A	13	Claude Code
convergegithub/spec-kit	Command	148k	today	MIT	A	35	Claude Code
speckit.bug.testgithub/spec-kit	Command	148k	today	MIT	A	13	Claude Code
analyzegithub/spec-kit	Command	148k	today	MIT	A	26	Claude Code

ai-agents-workspace-starter: Command for Claude Code