skills.rest
intent-integrity-chain
intent-integrity-chainOFFICIAL
Explore all skills by this author →
GitHub

iikit-03-plan

Translate a feature specification into a formal implementation plan with artifacts.

47|4|Updated Feb 3, 2026
Search Tags:#design#architecture#implementation#constitution#plan#contracts#iikit
One-click install
npx skills add https://github.com/intent-integrity-chain/kit --skill iikit-03-plan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: iikit-03-plan
Source: https://github.com/intent-integrity-chain/kit/tree/main/.claude/skills/iikit-03-plan
Command: npx skills add https://github.com/intent-integrity-chain/kit --skill iikit-03-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill translates a feature specification into a structured implementation plan, aligning design, contracts, and data models for fast, accountable delivery.

Core Features & Use Cases

  • Automated Plan Generation: Convert a feature spec into a comprehensive plan with technical context, gates, and artifact templates.
  • Artifact Production: Generate data-model.md, contracts/, quickstart.md, and an initial IMPL_PLAN outline from the spec.
  • Clarification Handling: Document assumptions and unresolved questions to ensure governance and traceability.

Quick Start

Start by placing a feature specification in specs/[FEATURE] and run the iikit plan command to generate artifacts, review the results in specs/[FEATURE]/plan.md and related outputs.

Frequently Asked Questions about iikit-03-plan

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

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

Feature specifications translate into implementation plans using constitution-driven gates that validate completeness and generate data models, contracts, and quickstart guides. Run the iikit plan command on your spec to produce structured artifacts ready for downstream phases.

What artifacts does the planning phase produce?▼

The planning phase generates data-model.md defining your data structures, contracts/ documenting interfaces, quickstart.md for onboarding, and an IMPL_PLAN outline. These outputs capture assumptions and unresolved questions for governance and traceability throughout implementation.

When should I use architecture and design planning before implementation?▼

Design planning ensures fast, accountable delivery by aligning technical context, gates, and contracts before coding begins. It documents assumptions upfront, prevents misalignment between teams, and produces reusable artifact templates that downstream phases consume consistently.

Can I use this with existing specifications and data models?▼

Yes. Place your feature specification in specs/[FEATURE] and the planning process integrates with your existing data structures. It validates and enriches your spec with formal contracts, gates, and implementation context without requiring restructuring.

What governance does the planning phase enforce?▼

Constitution-driven gates validate plan completeness and enforce structured decision-making. Clarifications and unresolved questions surface during planning, creating an audit trail and ensuring stakeholders address gaps before implementation begins.

Related Skills

Explore More Software Engineering Skills→
Snowflake-LabsSnowflake-Labs
12

read-ors-configuration

A concise summary of your roleplay character: name,</name> personality, and/or behavior, formatted as a single string sentence. Typically不超过50字，此处省略

Official
Intermediate
ATTCKDigitalATTCKDigital
50

smith-plan

Converts feature specifications into structured implementation plans and artifacts for software projects.

Official
Advanced
PiklarPiklar

speckit-plan

Generate technical design artifacts and research documentation from feature specifications.

Community
Advanced
NodeJSmithNodeJSmith
1

mine.design

Scope requirements, investigate codebases, and generate formal design documents.

Community
Advanced