agentsclimarketplace

Spec finish

Skill martinffx/atelier/skills/spec-finish

Post-implementation completion workflow for Spec-backed Plans. Use after spec-implement completes to validate, review, create stacked commits, and open a PR via code-pull-request. Triggers only with an active Spec-backed Plan after spec-implement completes, including when the user says "finish", "done", or "complete" in that context.From its SKILL.md

Install
npx -y skills add martinffx/atelier --skill spec-finish

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

SKILL.md

4.2 KB, as published. Nobody here has run it

Spec Finish

Post-implementation workflow: simplify → synchronize docs → validate → review → prepare PR.

Prerequisites

Before starting, verify:

  1. All Spec-backed Plan tasks are complete
  2. Working directory has no unresolved staged or unstaged changes
  3. Tests pass

If not complete, go back to spec-implement.


Step 1: Compare Scope and Simplify

Compare the implementation with the original behavior and user goal before documentation or validation. Remove unrequested scope, duplicate concepts, one-consumer abstractions, and custom machinery that replaces sufficient platform behavior.

If the implementation faithfully follows an unnecessarily large design, stop and return to spec-plan. Get approval for the smaller plan before continuing.

Update the finished SDD to describe the smaller result. Replace rejected architecture in the normative design and plan instead of preserving it as precedent; mention it only as a rejected alternative when that history remains useful.


Step 2: Update Documentation

Check whether README, API documentation, or changelog updates are needed. Make and commit any necessary documentation changes through code-commit before final validation.


Step 3: Validate

Run validation checks.

Test Suite

npm test
# or
pytest
# or
cargo test

Type Check

npm run typecheck
# or
python -m mypy
# or
cargo check

Lint

npm run lint
# or
ruff check .
# or
cargo clippy

Build

npm run build
# or
go build ./...

If any fail: Return to spec-implement to fix.

If all pass: Proceed.


Step 4: Review

Invoke the installed code-review skill through the harness's skill mechanism for one comprehensive review of the final change.

What to Review

  • All changed files since the intended base branch's merge base
  • Test coverage
  • Documentation updates
  • No debug code left

If code-review finds issues

  • Minor fixes may be made here, then re-validated and reviewed.
  • Blocking or scope-changing fixes return to spec-implement.

Step 5: Prepare Commits

Review current commits with git log --oneline. Use code-commit for any uncommitted work. Do not rewrite history by default. If a rebase would materially improve an unpublished stack, show the affected range and ask for separate approval before rebasing.


Step 6: Prepare the PR

Steps 1-5 (simplification, documentation, validation, review, commits) must all be complete before proceeding. If code-review found blocking or scope-changing issues, stop and return to spec-implement to fix them. Do not proceed to Step 6b.

Step 6a: Present Completion Summary

Before creating the PR, present a summary to the human:

## Completion Summary

**Feature:** [name]
**Tests:** [passed/failed]
**Type Check:** [passed/failed]
**Lint:** [passed/failed]
**Review:** [passed/issues found]
**Commits:** [N commits in stack]
**Ready for PR:** [yes/no]

Step 6b: Invoke code-pull-request

Only when the summary shows Ready for PR: yes, invoke the code-pull-request skill to create the PR. It detects the platform (GitHub/GitLab), checks for an existing PR, finds a template, generates the body from commits, and opens the PR via gh or glab.

Handoff

"Implementation complete. [N] commits are ready. PR package ready for approval."


Integration

This skill orchestrates other skills:

  • Invokes code-review for quality check
  • Invokes code-pull-request as the final step to open the PR

When NOT to Use

  • If implementation is still in progress, use spec-implement
  • If tests are failing, go back to spec-implement
  • If review found blocking or scope-changing issues, go back to spec-implement
  • If the implementation follows an unnecessarily large design, go back to spec-plan

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most plan spec skills give

Counted across 1,360 of the 2,617 authors here whose files we hold, read 2026-09-06

  • Ask one question at a timein 73 of 1360
  • Write the spec using the templatein 22 of 1360
  • Ask clarifying questions if neededin 19 of 1360, across 18 files
  • Wait for user confirmation before proceedingin 19 of 1360
  • Save plans to the plans directoryin 17 of 1360, across 13 files
  • Check for product marketing context firstin 16 of 1360, across 5 files
  • Read the plan file completelyin 16 of 1360
  • Order tasks by dependencyin 16 of 1360
  • Gather context from the conversationin 15 of 1360, across 9 files
  • Explore the codebase instead of askingin 15 of 1360, across 13 files
  • Wait for explicit user approvalin 14 of 1360, across 13 files
  • Quiz the user on the breakdownin 13 of 1360, across 7 files

Said here and by no other author read

  • Verify working directory has no unresolved changes
  • Remove unrequested scope and duplicate concepts
  • Update the finished SDD to describe the smaller result
  • Use code-commit for any uncommitted work
  • Invoke code-pull-request to create the PR

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.

Keep looking

Skills are one crate of 614,496. 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.