kn-plan

Convert high-level objectives into reviewable implementation plans with approval gates.

234|50|Updated Dec 25, 2025
One-click install
npx skills add https://github.com/knowns-dev/knowns --skill kn-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kn-plan
Source: https://github.com/knowns-dev/knowns/tree/main/.agent/skills/kn-plan
Command: npx skills add https://github.com/knowns-dev/knowns --skill kn-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams convert high-level tasks into concrete, executable plans by gathering context, outlining steps, and validating the plan before seeking explicit approval.

Core Features & Use Cases

  • Context gathering: collect relevant docs, specs, and templates to clarify scope.
  • Plan drafting: generate a structured implementation plan with steps, dependencies, and acceptance criteria.
  • Validation & approval: verify references and wait for explicit approval before proceeding to task creation; supports an MCP-based workflow.
  • Task creation from specs: transform specifications into actionable tasks linked to the source spec.

Quick Start

Announce planning in the task channel and start by gathering context, generating a plan, and awaiting approval before creating tasks.

Frequently Asked Questions about kn-plan

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

FAQPage Schema
How do I convert a high-level objective into an actionable implementation plan?

To create an implementation plan, you gather context from docs and specs, draft structured steps with dependencies and acceptance criteria, and validate references before awaiting explicit approval. This ensures the plan is actionable and traceable before proceeding to task creation.

What is the best way to enforce an approval gate before creating tasks from specs?

Enforcing an approval gate requires pausing task creation until explicit approval is granted after plan validation. The workflow updates task statuses via MCP commands to ensure traceability, preventing unreviewed specifications from becoming actionable tasks.

How does gathering context from docs and specs improve task planning?

Gathering context from docs and specs clarifies the scope by collecting relevant templates and references before drafting the plan. This ensures the generated implementation steps align with existing documentation and validation checks pass successfully.

Can I use MCP commands to fetch docs and update task statuses during workflow planning?

Yes, you can use MCP commands to fetch docs and tasks during context gathering and update task statuses once the plan is approved. This MCP-based workflow ensures traceability throughout the drafting, validation, and task creation phases.

Does task planning work without explicit approval for creating tasks?

No, task planning enforces an explicit approval gate before transforming specifications into actionable tasks. The workflow validates the drafted plan and waits for user approval to ensure no tasks are created without a reviewed and accepted implementation strategy.