speckit-plan

Generate technical design artifacts and research documentation from feature specifications.

Updated May 31, 2026
One-click install
npx skills add https://github.com/Piklar/Rizza-60 --skill speckit-plan-piklar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-plan
Source: https://github.com/Piklar/Rizza-60/tree/main/.agents/skills/speckit-plan
Command: npx skills add https://github.com/Piklar/Rizza-60 --skill speckit-plan-piklar

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the transition from feature specification to technical implementation by automating the generation of design artifacts and research documentation.

Core Features & Use Cases

  • Automated Planning: Orchestrates the creation of technical specifications, data models, and interface contracts based on project templates.
  • Research Integration: Automatically identifies unknowns in technical requirements and dispatches research tasks to resolve them.
  • Use Case: When starting a new feature, use this Skill to generate a comprehensive implementation plan, define data models, and establish API contracts, ensuring all technical requirements are validated against project constitution rules.

Quick Start

Invoke the speckit-plan skill to generate the implementation plan and design artifacts for the current feature specification.

Frequently Asked Questions about speckit-plan

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

FAQPage Schema
How do I automate technical design generation from feature specifications?

Automating technical design generation from feature specifications involves orchestrating the creation of data models, interface contracts, and research summaries. This process validates technical requirements against project constitution rules to streamline implementation planning.

What is the best way to define API contracts and data models for a new feature?

The best way to define API contracts and data models for a new feature is to use an automated planning workflow that generates technical design artifacts. This validates interface contracts against project-specific constitution rules and templates.

How do I identify and resolve technical unknowns during implementation planning?

Identifying and resolving technical unknowns during implementation planning requires research integration. The workflow automatically dispatches research tasks to resolve ambiguities in technical requirements and generates research documentation.

Can I use project-specific constitution rules to validate my architecture specifications?

Yes, you can use project-specific constitution rules to validate architecture specifications. The planning workflow requires adherence to these rules and integrates with defined extension hooks for pre- and post-execution tasks.

How do I integrate pre-execution and post-execution tasks into a specification workflow?

Integrating pre-execution and post-execution tasks into a specification workflow requires using defined extension hooks. This ensures the automated generation of design artifacts respects project-specific constitution rules and structural templates.