complete

Complete a task with full validation, documentation updates, reviews, and automatic merge to develop.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "complete" with this command: npx skills add taylorhuston/local-life-manager/taylorhuston-local-life-manager-complete

/complete

Complete a task with full validation, documentation updates, reviews, and automatic merge to develop.

Usage

/complete careerbrain 002 # Complete specific issue /complete careerbrain # Complete current/active issue

What It Does

  • Validate PLAN completion and spec compliance

  • Update all project documentation

  • Create final commit with doc changes

  • Run mandatory code review + security audit

  • Merge to develop branch

  • Clean up feature branch

GitFlow Pattern: feature/* → develop (automatic) | develop → main (requires PR)

Prerequisites

  • All implementation complete (code written)

  • Active issue with completed work

  • PLAN.md exists with phases mostly complete

Execution Flow

  1. Check PLAN.md Completion

✓ All phases complete (5/5) or ✗ Incomplete phases:

  • 1.3 - Implement session refresh
  1. Spec Compliance Validation

Acceptance Scenario Coverage:

  • Search tests matching each Given/When/Then scenario

  • Create missing tests if needed

Success Metrics Verification:

  • Check performance, coverage, accessibility

Out-of-Scope Enforcement:

  • Scan for code that violates out-of-scope items

Agent Constraints Check:

  • Verify no dependencies added (if constrained)

  • Check no files outside scope modified

  1. Update Spec Status Markers

If the TASK has an implements: field, update inline status markers in the spec:

Before (in spaces/[project]/docs/specs/*.md)

  • 🚧 User registration with email/password

After

  • ✅ User registration with email/password

This provides public visibility into what's implemented.

  1. Update All Documentation

Scan and validate ALL docs in spaces/[project]/docs/ :

  • architecture-overview.md

  • data-model.md

  • api-overview.md

  • README.md

  1. Update CHANGELOG

MANDATORY: Add entries under [Unreleased] section.

Categories:

  • Added

  • New features (TASKs)

  • Fixed

  • Bug fixes (BUGs)

  • Changed

  • Modifications

  • Security

  • Security updates

  1. Final WORKLOG Entry

YYYY-MM-DD HH:MM - COMPLETED

Issue ### complete and ready for merge.

Summary:

  • [What was implemented]
  • [What was deferred]
  1. Update Status

Set issue frontmatter: status: complete

  1. Create Final Commit

Stage and commit documentation changes.

  1. Run Final Reviews

If not already done:

  • Launch code-reviewer agent

  • Launch security-auditor agent

  • Block if CRITICAL issues

  1. Merge to Develop

git checkout develop git pull origin develop git merge --no-ff feature/###-slug git push origin develop git branch -d feature/###-slug

  1. Suggest Next Steps

Next actions:

  1. Start next task: /implement project ### --full
  2. View status: /project-status project
  3. Merge to main (requires PR): gh pr create --base main --head develop

Documentation Checklist

Before merge, verify:

  • PLAN.md - All phases checked off

  • Linked SPEC - Updated to reflect what was built

  • architecture-overview.md - Reflects changes

  • ADRs - New decisions documented

  • CHANGELOG.md - User-facing changes

  • WORKLOG.md - Final summary

  • README.md - Updated if API changed

Workflow

/issue → /plan → /implement → /commit → /complete ↓ Update docs + CHANGELOG ↓ Run reviews ↓ Merge to develop

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

General

daily-review

No summary provided by upstream source.

Repository SourceNeeds Review
General

weekly-review

No summary provided by upstream source.

Repository SourceNeeds Review
General

daily-journal

No summary provided by upstream source.

Repository SourceNeeds Review