kf-developer

Validate and implement Kiloforge track IDs using parallel worktrees.

2|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/Kiloforge/kiloforge-skills --skill kf-developer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kf-developer
Source: https://github.com/Kiloforge/kiloforge-skills/tree/main/kf-developer
Command: npx skills add https://github.com/Kiloforge/kiloforge-skills --skill kf-developer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Receive a track ID, validate it is an active unclaimed track, then implement it following the kiloforge workflow.

Core Features & Use Cases

  • Validate and claim a track
  • Create implementation worktrees and branches
  • Execute the plan with optional TDD workflow, verification, and merge protocol
  • Ensure compliance with track specs and registry updates

Quick Start

Provide a track ID to begin implementing the selected Kiloforge track.

Frequently Asked Questions about kf-developer

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

FAQPage Schema
How do I automate track implementation with git worktree parallel branches?

To automate track implementation with git worktree parallel branches, provide a track ID to validate and claim it, then execute the configured workflow for branch creation, task implementation, verification, and merge.

What is the kiloforge workflow for managing track lifecycles?

The kiloforge workflow manages track lifecycles through pre-flight checks, automatic heartbeat lock management, structured commit strategies, and registry updates to ensure compliance with track specifications.

How do I validate and claim an active track before starting development?

Validate and claim an active track by providing its track ID; the system performs pre-flight checks to confirm the track is active and unclaimed before authorizing implementation.

Can I use TDD workflow and verification during track implementation?

Yes, you can execute the plan with an optional TDD workflow, running verifications before proceeding to the merge protocol to ensure the implementation meets the configured track specifications.

How does automatic heartbeat lock management work for active tracks?

Automatic heartbeat lock management maintains your claim on an active track during implementation, preventing other developers from claiming the same track while you execute the worktree workflow.

What is the best way to handle branch creation and merge for development tracks?

The best way to handle branch creation and merge for development tracks is using the parallel worktree workflow, which automates branch setup, implementation, and eventual merge according to configured workflow rules.