iikit-02-plan

Generate technical design documents with data models and API contracts from feature specifications.

1|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/hafidzlvm/opencode --skill iikit-02-plan-hafidzlvm
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: iikit-02-plan
Source: https://github.com/hafidzlvm/opencode/tree/main/.tessl/tiles/tessl-labs/intent-integrity-kit/skills/iikit-02-plan
Command: npx skills add https://github.com/hafidzlvm/opencode --skill iikit-02-plan-hafidzlvm

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Turning a feature specification into a concrete technical design requires choosing frameworks, defining data models, and writing API contracts, which is time-consuming and error-prone when done manually. This Skill automates that planning phase by generating a structured implementation plan from an existing spec.md file. ## Core Features & Use Cases - Spec Quality Gate: Scores the feature specification out of 10 by checking requirement counts, measurable success criteria, unresolved clarifications, and story coverage before planning begins. - Design Artifact Generation: Produces research.md, data-model.md, API contracts, and quickstart.md from the spec, with dependency-ordered implementation strategy. - Constitution Enforcement: Validates every technical decision against project governance principles and halts on violations with compliant alternatives. - Use Case: After writing a feature spec for a new checkout flow, run this Skill to select the tech stack, define the PostgreSQL schema, generate REST API contracts, and produce a semantic diff when re-planning. ## Quick Start Run the plan skill to generate a technical design document from my current feature specification.

Frequently Asked Questions about iikit-02-plan

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

FAQPage Schema
How do I generate a technical design document from a feature spec?▼

Run the plan phase after creating a spec.md with the specify step. The skill validates spec quality, fills a technical context template, researches unknowns into research.md, and generates data models, API contracts, and quickstart scenarios.

What artifacts does a spec-driven implementation plan produce?▼

The planning phase produces plan.md, research.md with technology decisions and rationale, data-model.md with entities and validation rules, API contracts in a contracts directory, and quickstart.md with test scenarios.

What happens if my spec quality score is too low before planning?▼

The skill computes a spec quality score out of 10 based on requirements, measurable criteria, clarifications, and story coverage. If the score is below 6, it recommends running the clarify step first to resolve ambiguities.

Does the plan skill work without a project constitution file?▼

No, the plan phase requires CONSTITUTION.md in hard enforcement mode. If it is missing, the prerequisite check fails and instructs you to run the constitution step first, since all technical decisions are validated against governance principles.

What happens when I re-run planning on an existing plan?▼

On re-runs, the skill regenerates the plan and outputs a semantic diff showing added, changed, and removed tech stack items, architecture components, and dependencies, plus downstream impact warnings for artifacts like tasks.md.