kiwi-planner

Plan software requirements into phases and tasks using SpecKiwi.

1|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/Snoworca/speckiwi --skill kiwi-planner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kiwi-planner
Source: https://github.com/Snoworca/speckiwi/tree/main/skills/claude/kiwi-planner
Command: npx skills add https://github.com/Snoworca/speckiwi --skill kiwi-planner

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires specckiwi, codex, claude, opencode, hermes, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill helps you plan and implement software requirements using a single shared view, streamlining the process from authoring to feasibility review, implementation planning, and more.

Core Features & Use Cases

  • Requirement Authoring: Author Markdown SRS documents as the canonical source of requirements.
  • Feasibility Review: Connect requirement authoring with implementation planning and TDD-based coding.
  • Implementation Planning: Plan and structure requirements into phases and tasks.
  • SRS Synchronization: Keep requirements in sync with commits and pushes.
  • Use Case: Suppose you have a new project with complex requirements. Use the kiwi-planner skill to author the requirements, plan the implementation, and ensure synchronization with the codebase.

Quick Start

Use the kiwi-planner skill to initialize a new project and create a plan for the active requirements.

Frequently Asked Questions about kiwi-planner

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

FAQPage Schema
How do I plan software requirements into implementation phases?

To plan software requirements into implementation phases, you author Markdown SRS documents as the canonical source, then structure them into phases and tasks using a workflow that connects requirement authoring with feasibility review and TDD-based coding.

What is the best way to keep requirements in sync with codebase commits?

The best way to keep requirements in sync with codebase commits is to use an SRS synchronization workflow that ties Markdown requirement documents directly to your implementation planning, coding, commit, and push processes.

Do I need SpecKiwi to implement TDD-based coding from a specification?

Yes, you need SpecKiwi and a supported coding agent to implement TDD-based coding from a specification, because the workflow relies on SpecKiwi to synchronize requirement authoring, feasibility review, and implementation planning with the codebase.

Can I use kiwi-planner with codex or claude for implementation planning?

Yes, you can use kiwi-planner with coding agents like codex, claude, opencode, and hermes for implementation planning, as these are supported dependencies for synchronizing requirements with TDD-based coding tasks.

How does requirement authoring connect with feasibility review and TDD coding?

Requirement authoring connects with feasibility review and TDD coding through a single shared view that uses Markdown SRS documents as the canonical source, bridging the gap between planning phases and actual test-driven implementation tasks.

When should I not use an SRS synchronization workflow for software requirements?

You should not use an SRS synchronization workflow for software requirements if your project lacks complex requirement structures or does not utilize test-driven development, as the process is designed to tightly couple SRS documents with phased TDD coding and commit synchronization.