skills.rest
dikini
dikiniCOMMUNITY
Explore all skills by this author →
𝕏@dikiniGitHub

bk-plan

Generate implementation plans from technical specifications with task dependencies and effort sizes.

Updated Mar 3, 2026
Search Tags:#planning#roadmap#implementation plan#task decomposition#dependency mapping#spec to plan
One-click install
npx skills add https://github.com/dikini/knot --skill bk-plan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bk-plan
Source: https://github.com/dikini/knot/tree/main/.agents/skills/bk-plan
Command: npx skills add https://github.com/dikini/knot --skill bk-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill transforms abstract specifications into detailed, actionable implementation plans, breaking down complex features into manageable tasks with clear dependencies.

Core Features & Use Cases

  • Task Decomposition: Breaks down requirements into granular tasks (foundation, core logic, interfaces, testing, integration).
  • Dependency Mapping: Identifies and visualizes task dependencies to create a logical workflow.
  • T-shirt Sizing: Assigns effort estimates (S, M, L) for better project scoping.
  • Use Case: After a feature specification is drafted, use this Skill to generate a clear roadmap of development tasks, estimate their complexity, and identify the critical path for implementation.

Quick Start

Use the bk-plan skill to create an implementation plan for the attached spec file.

Frequently Asked Questions about bk-plan

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

FAQPage Schema
How do I convert a technical specification into an implementation plan?▼

Converting a spec into an implementation plan involves decomposing features into granular tasks, mapping dependencies, and assigning T-shirt effort sizes to create a logical development workflow.

What is the best way to map task dependencies for a software roadmap?▼

Mapping task dependencies for a software roadmap requires identifying foundational, core logic, and testing tasks to visualize sequential, parallel, or milestone-driven workflows.

Can I generate both human-readable and machine-readable project plans?▼

Yes, you can generate both human-readable Markdown documents and machine-readable YAML plans, alongside updating a roadmap index for integrated project tracking.

Does task decomposition support milestone-driven development approaches?▼

Task decomposition supports milestone-driven development approaches, allowing you to structure sequential or parallel task workflows while applying optional constraints to the project scope.

How are effort estimates calculated during feature decomposition?▼

Effort estimates during feature decomposition are assigned using T-shirt sizing (S, M, L), providing a clear metric for project scoping and identifying the critical path for implementation.

Related Skills

Explore More Software Engineering Skills→
Tristan578Tristan578
5

planner

Draft SpawnForge feature specs with acceptance criteria and success metrics.

Community
Advanced
mpazarynampazaryna
1

roadmap

Read and update `.orchestra/roadmap.md` and PRD documents for project status.

Community
Intermediate
luanluan
4

commit

Create conventional Git commits and sync them with issue tracking systems.

Community
Intermediate
infantesromeroadrianinfantesromeroadrian

ml-code-store-promote

Migrate code to an ml-code-store and generate git diffs and unit tests.

Community
Advanced