Skip to content
Back to skills

Implement

ASecurity

Build ready pieces. Typed alone, take one free or ask which. Given a piece, request or "auto", follow its route; it does not shape.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 21, 2026
developmentpythongogit

Security analysis

A100/100

Pro scans all 3 files and shows the line behind each finding

Scanned October 21, 2026

npx -y skills add gwpicard/ai-build-kit --skill implement --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Implement?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Implement
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/gwpicard-implement/badge)](https://www.skillsdirectory.com/skills/gwpicard-implement)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: implement
description: Build ready pieces. Typed alone, take one free or ask which. Given a piece, request or "auto", follow its route; it does not shape.
---

# Implement

Read `masterplan.md` (risk record first) and refresh the plan with
`sh .agents/tools/plan-refresh.sh`. See `records/references/pieces.md`.
Run `maintain/scripts/upgrade-check.py` from the project root and keep
only its exit code. Exit 1 means `/maintain` must finish the update; say so
and carry on.

In Codex, on `unable to get password from user`, run the installed setup
skill's `templates/foundation/codex-github-check.py` with python3 and
`--message`. Give its sentence and stop. Do not retry or sign in.

## Choose work

A ready repair comes first. Otherwise take the only free ready piece. If several are ready, show them and their blockers, then
ask which to take. Unattended, take the lowest-numbered.

A piece must be ready, have `## Done when`, and wait on no question. A piece with open parts is a container; build its parts. Send an unready piece to
`/shape` with the reason; it does not settle the question. A plain
request must match a ready piece or goes to `/shape`. For a live break, follow
`live-copy`'s rollback route.

Skip questions, missing `Done when`, `## Waiting on you`, unmet dependencies,
another person's assignment or a recorded block. Say why; take the next
eligible piece. Closed blockers make `blocked` stale; say so. Mutual blockers
go to `/shape`.

For several ready pieces, show **Ready now** and **Waiting**, counts and dependencies. Omit questions; an unmarked piece needs
`/shape`. Showing a list builds nothing. A green pull request waits for merge;
follow `merge` only when asked. Ask which merge when told only "put it live".

## Build and save

Build one piece per pass with `build-piece`, through updated records. After
green checks and records in the pull request, use `merge`. By default, a named
yes is required to merge. Unattended, leave it ready for review unless the
automatic merge option is on.

`auto` needs approval and `references/running-longer.md`. An unattended run merges only through `--auto` when the setting is on, never otherwise. Each piece must be
self-sufficient enough to build without a person present. Load the reference
first. In an unattended run nobody is there to say yes, so never merge except
through `--auto` when its recorded option and every hold allow it, and never
accept a risk for the person.

## Done when

Evidence, review, records and save route are complete, with any available
machine check run and green; or report a safe block, its caution and other
work. Never call blocked work ready or live.

Files in this skill

  • SKILL.md2.6 KB
  • references/running-longer.md2.6 KB
  • scripts/attempt.sh1.9 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.