feature-complete

Archive feature working files after a pull request is merged.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/telefrek/jlsm --skill feature-complete-telefrek
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-complete
Source: https://github.com/telefrek/jlsm/tree/main/.claude/skills/feature-complete
Command: npx skills add https://github.com/telefrek/jlsm --skill feature-complete-telefrek

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of archiving feature working files once a pull request (PR) has been merged, streamlining the feature lifecycle management.

Core Features & Use Cases

  • Automated Archive: Moves feature working files to an archive directory post-merge, preserving the working state without cluttering the main repository.
  • Status Verification: Checks the feature's status before archiving to ensure the refactor stage is complete.
  • Narrative Generation: Attempts to generate a narrative file if it doesn't exist before archiving the feature.
  • Work Group Management: Updates work group manifests and readiness caches for features that belong to a work group.

Quick Start

Run the command: /feature-complete <feature-slug>

Frequently Asked Questions about feature-complete

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I archive feature working files automatically after a pull request merge?

You can archive feature working files after a pull request merge by running a script that checks the refactor stage status, moves the files to an archive directory, and updates work group manifests.

Can I generate a missing narrative file before moving a feature to the archive?

Yes, the archival process attempts to generate a narrative file automatically if it does not already exist before moving the feature working files to the archive directory.

Does the feature archival process update work group manifests and readiness caches?

Yes, work group manifests and readiness caches are updated automatically during the archival process for features that belong to a specific work group.

What is the best way to verify feature status before archiving working files?

The best way to verify feature status is to execute a status check script that ensures the refactor stage is fully complete before allowing the archival process to proceed.

Do I need script execution to manage feature lifecycle and code repository cleanup?

Yes, script execution is required to run the archive and status checks needed for managing the feature lifecycle and cleaning up the code repository after a merge.