agentsclimarketplace

Implement

Skill lasswellt/blitz-cc/skills/implement

Runs the implementation phase of a sprint by routing to sprint-dev. Use when the user says 'implement sprint N', 'develop these stories', or 'resume sprint'. Skip planning and review — those are separate skills. Thin router: identical effect to /blitz:sprint-dev; unlike /blitz:sprint it does not plan or review.From its SKILL.md

Install
npx -y skills add lasswellt/blitz-cc --skill implement

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.3 KB, as published. Nobody here has run it

OUTPUT STYLE: terse-technical per /_shared/terse-output.md. Drop articles, fillers, pleasantries, hedging. Preserve verbatim: code fences, inline code, URLs, file paths, commands, grep patterns, YAML/JSON, headings, table rows, error codes, dates, version numbers. No preamble. No trailing summary of work already evident in the diff or tool output. Format: fragments OK.

Sprint Implementation

You run the implementation phase of a sprint.

Session registration: follow session-lifecycle.md §Session Registration before any other work.

Verbose progress is mandatory. Follow terse-output.md throughout. Print [implement] prefixed status lines at every phase transition, decision point, and when dispatching to sprint-dev. Log skill_start and skill_complete events to the activity feed (.cc-sessions/activity-feed.jsonl).

Dispatch

implement is a thin ergonomic verb. It owns no flags or validation of its own — it forwards verbatim to sprint-dev, which is the single source of truth for flag semantics (--sprint, --stories, --resume, --mode), pre-flight (its Phase 0.0 hard-fails on a missing manifest/stories), and the Definition of Done.

  1. If no args are given, check for an in-progress sprint with a STATE.md and offer --resume; otherwise ask which sprint/stories to implement.
  2. Invoke the sprint-dev skill, passing the user's arguments through unchanged.

sprint-dev handles everything downstream — story reading, agent waves, tests, verification, progress reporting. Do not duplicate its logic here; if a flag changes, it changes in sprint-dev only.

Keep looking

Skills are one crate of 627,801. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.