run-feature-complete

name	run-feature-complete
description	Updates documentation and guides, verifying the feature implementation before marking it complete.

Run Feature Complete Skill

Execute this skill when a feature implementation has been verified and is ready for release. This skill executes the workspace-customized instructions located in docs/prompts/feature-complete.md.

Source of Truth Principle: All documentation updates must be driven by what exists in the codebase (e.g., package.json files, model definitions, config files), not by what the AI remembers from the conversation. Verify all version numbers, file paths, and tech references against actual source files before writing.

Step 1: Read the Workspace-Customized Feature Complete Prompt

Read docs/prompts/feature-complete.md and execute the instructions contained within it in full.

[!NOTE] If the file contains only a placeholder/disclaimer (i.e., /generate-review-prompts has not been run yet), fall back to the default feature-complete procedure below.

Default Feature Complete Procedure

Use this procedure if docs/prompts/feature-complete.md has not yet been generated by /generate-review-prompts.

1. Identify the Completed Feature

Review the recent conversation history, task.md, and implementation_plan.md to identify the specific feature that was just completed.

2. Update Project Management Artifacts

• implementation_plan.md: Mark all relevant steps as [x] (Completed).
• task.md: Mark the top-level task and sub-tasks as [x].

3. Update Project Documentation

• docs/project/backlog.md: Move the feature from "Backlog" or "In Progress" to "Completed". Mark resolved technical debt items as [x].
• docs/project/feature-status.md: Update the feature status to "Completed" / "Live".
• docs/project/roadmap.md: Check off the milestone corresponding to this feature.

4. Update Project Rules & Modular Skills (If Applicable)

• Architecture or stack changes → Update GEMINI.md.
• New reusable capabilities → Update or create the relevant skill in skills/.
• Common gotchas → Update GEMINI.md.

5. Update Knowledge Base & Other Docs

Scan for any documentation that might be outdated by this change and update accordingly.

6. Update CHANGELOG.md

1. Run git log to list commits included in this release.
2. Run git diff --name-status to enumerate changed files.
3. Write a new version entry following Keep a Changelog format.
4. Default version bump: PATCH (x.y.Z+1) unless the user explicitly instructs otherwise.

7. Final Verification

• Verify all links between documents are valid.
• Confirm CHANGELOG.md has been updated.
• Run git tag --list to confirm the new version doesn't conflict with an existing tag.

8. Commit, Tag & Push (USER ACTION — Required)

[!IMPORTANT] The AI's git boundary ends at staging (git add). All commands below are USER-ONLY. The AI must call these out explicitly so the user knows what to execute.

# 1. Commit all staged changes
git commit -m "docs: feature-complete vX.Y.Z — <Feature Name>"

# 2. Create the release tag
git tag vX.Y.Z

# 3. Push the commit AND the tag together
git push origin main --tags