kspec-plan

Convert approved plans into linked specs and tasks with audit trails.

1|2|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/lepahc/kynetic-spec --skill kspec-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kspec-plan
Source: https://github.com/lepahc/kynetic-spec/tree/main/.agents/skills/kspec-plan
Command: npx skills add https://github.com/lepahc/kynetic-spec --skill kspec-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translate approved plans into durable, auditable specs and tasks that link to derived work, enabling traceability across sessions.

Core Features & Use Cases

  • Convert approved plans into spec/task structures for execution
  • Choose import or manual paths, derive specs, and track progress
  • Support plan branching and audit trails via shadow branches

Quick Start

Import an approved plan and derive its specs and tasks to begin execution.

Frequently Asked Questions about kspec-plan

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

FAQPage Schema
How do I convert approved plans into specs and tasks for execution?

You can convert approved plans into specs and tasks by importing the plan document and deriving linked, auditable spec and task structures to begin execution.

What is the best way to maintain an audit trail for plan-to-spec workflows?

The best way to maintain an audit trail for plan-to-spec workflows is to use shadow branches, which track plan states and provide traceability across sessions for derived work.

Can I branch plans on shared branches without losing traceability?

Yes, you can branch plans on shared branches using shadow branches, which preserve the audit trail and maintain links between the approved plan and derived specs.

Do I need clear plan documents to derive specs and tasks?

Yes, you need clear plan documents as a prerequisite; the workflow requires approved planning artifacts to accurately import, derive specs, and track execution progress.

Does this workflow support manual paths instead of importing plans?

Yes, the workflow supports both import and manual paths, allowing you to choose how to derive specs and tasks from approved plans based on your execution needs.

Why does plan traceability matter across sessions?

Plan traceability matters across sessions because it translates approved plans into durable specs and tasks, linking derived work back to the original plan for continuous auditability.