Manage Kiloforge track lifecycles with version-controlled archiving, restoration, and cleanup.
npx skills add https://github.com/Kiloforge/kiloforge-skills --skill kf-manage
Please help me install this Agent Skill. Skill: kf-manage Source: https://github.com/Kiloforge/kiloforge-skills/tree/main/kf-manage Command: npx skills add https://github.com/Kiloforge/kiloforge-skills --skill kf-manage
Kiloforge Track Manager enables teams to govern the full lifecycle of tracks—archiving completed work, restoring or deleting tracks, renaming identifiers, and cleaning up orphaned artifacts—while keeping the filesystem and registry in sync and safeguarded by explicit prompts and commits.
Run the interactive Track Manager to organize active, completed, and archived tracks.
High-intent search queries and answers about installing and using this skill.
You can archive completed tracks by moving them to the archive location and updating the registry, which ensures the filesystem and registry stay synchronized. Bulk archiving pushes a batch entry while preserving history.
Yes, you can restore an archived track back to active status with its metadata fully restored. The process includes explicit pre-flight checks to ensure safe restoration before the track is reactivated.
Cleaning up orphaned artifacts involves synchronizing tracks.yaml with the filesystem state to remove stray files. This process ensures the registry accurately reflects the physical workspace without losing active track data.
Renaming a track ID preserves history by recording the original identifier in a previous_ids list. This maintains a continuous version-controlled record across the track's lifecycle despite the identifier change.
Yes, permanently deleting a track requires explicit confirmation to prevent accidental data loss. The operation generates an audit trail and commits the change to maintain strict safety checks.
You should compact archived data to reclaim workspace space while preserving the historical record. This is applicable when accumulated archived tracks consume excessive storage but must remain accessible for auditing.
AtaraxiaEpiphanyExecute deterministic post-loop state transitions and agent dispatches for development tracks.
bvshiArchive completed change folders and update status in a git repository.
leonardoteodorooCoordinate Conductor tracks across spec.md, plan.md, and lifecycle stages.
systeminitCreate and manage GitHub pull requests across Git and Jujutsu.
