planner

Name: planner
Availability: InStock
Author: FlineDev

Investigates repositories and generates Spec.md to guide Generator and Evaluator workflows.

38|2|Updated Mar 31, 2026

Search Tags:#workflow #planning #codex #claude #planner #spec-generation #dual-model

Ready to run

npx skills add https://github.com/FlineDev/TandemKit --skill planner-flinedev

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: planner
Source: https://github.com/FlineDev/TandemKit/tree/main/skills/planner
Command: npx skills add https://github.com/FlineDev/TandemKit --skill planner-flinedev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

TandemKit Planner enables a structured, automated planning phase by investigating the repository, clarifying goals, and producing a Spec.md that guides both the Generator and the Evaluator.

Core Features & Use Cases

Independent repository investigation to surface questions, risks, and constraints.
Formal Spec.md generation including acceptance criteria and open questions for later rounds.
Guiding the Convergence workflow with Codex second opinions and explicit prompts for the Planner.
Non-intrusive, read-only analysis that does not modify code unless approval is given.

Quick Start

Launch the planner workflow to generate a Spec.md; the Planner will perform independent investigation, draft the spec, and present a plan for Codex review.

Frequently Asked Questions about planner

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

FAQPage Schema

How do I generate a Spec.md from repository investigation?▼

Generating a Spec.md requires investigating the repository, clarifying goals, and extracting actionable requirements to produce a detailed spec that guides the Generator and Evaluator.

What is dual-model planning in software engineering workflows?▼

Dual-model planning uses two models to converge on a repository strategy, where one drafts the spec and the second model, such as Codex, provides reviews and second opinions to guide the final output.

Does the planning workflow modify existing code during repository analysis?▼

The planning workflow performs non-intrusive, read-only analysis to surface risks and constraints, and does not modify existing code unless explicit approval is given by the user.

How do I use Codex second opinions to improve generated specs?▼

Using Codex second opinions to improve generated specs involves drafting a plan with the primary model, then routing the output through the Convergence workflow for Codex review to identify risks and refine requirements.

Can I extract open questions and acceptance criteria from code and docs automatically?▼

Extracting open questions and acceptance criteria from code and docs automatically is supported by the Planner's independent investigation phase, which surfaces constraints and formalizes them into a Spec.md for later rounds.

What are the limitations of automated spec generation for repository planning?▼

Automated spec generation for repository planning relies heavily on the quality of existing code and docs, and requires a separate convergence workflow with Codex to resolve ambiguities, meaning it cannot finalize a spec independently.