Skip to content
Back to skills

Feature Done

ASecurity

Run the end-of-feature gate across checks, project conventions, change-spec compliance, current truth, and the delivery receipt.

  • 2 stars
  • 0 votes
  • 0 copies
  • 4 views
  • Added September 3, 2026
developmentbashgit

Security analysis

A100/100

Scanned September 20, 2026

npx -y skills add shrekshrek/project-workflow --skill feature-done --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Feature Done?

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

Security grade badge for Feature Done
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/shrekshrek-feature-done/badge)](https://www.skillsdirectory.com/skills/shrekshrek-feature-done)

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: feature-done
description: Run the end-of-feature gate across checks, project conventions, change-spec compliance, current truth, and the delivery receipt.
---

# Feature Done

Match the user's language. Read `${CLAUDE_PLUGIN_ROOT}/docs/actions/feature-done.md` completely before acting. Fresh reviewer agents read their canonical specs; the main session reads one only when executing the allowed fallback.

Claude execution details:

- Resolve `$ARGUMENTS` through the shared active-feature rules; exclude `archive/`. Review applicability follows the actual risk and project requirements, not file names.
- Execute the complete canonical action with Bash against its selected Git population. A stop still writes the
  canonical receipt.
- Resolve the canonical convention population and dispatch `spec-reviewer` and `agents-md-reviewer` as directed.
  Claude L2 may include project-root `.claude/rules/`; include user-level `~/.claude/rules/` only when selected.
- Capture the reviewed Git identity before endpoint-owned writes, then persist and structurally re-read the canonical `## Proof Bundle` receipt. For a non-READY verdict, map each blocker or blocker group to the canonical `Next` route before returning control under the action's continuation rules. Return the canonical action's `User handoff` summary.

Apply the canonical verdict and closure-authorization rules; when closure is authorized, continue to
`/project-workflow:feature-archive` for the explicit feature. Otherwise leave archive pending.

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.