skills.rest
yangsi7
yangsi7COMMUNITY
Explore all skills by this author →
GitHub

Implementation Planning

Generate technical implementation plans with architectural decisions and artifacts.

1|Updated Oct 24, 2025
Search Tags:#data modeling#implementation plan#technical planning#SDD#API contracts#architecture design#constitutional gates
One-click install
npx skills add https://github.com/yangsi7/skill-builder --skill implementation-planning
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Implementation Planning
Source: https://github.com/yangsi7/skill-builder/tree/main/.claude/skills/create-implementation-plan
Command: npx skills add https://github.com/yangsi7/skill-builder --skill implementation-planning

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires project-intel.mjs, MCP Ref, MCP Context7, Read, Write, Edit, and includes examples (resource) and references (resource) and workflows (resource) components.

What problem does it solve?

This Skill bridges the gap between high-level specifications and concrete technical implementation, preventing ad-hoc architectural decisions and costly rework. It ensures technical plans are robust, constitutionally compliant, and intelligence-backed.

Core Features & Use Cases

  • Constitutional Gatekeeping: Validates design against predefined complexity limits (e.g., max 3 projects, max 2 abstraction layers) both before and after technical design.
  • Intelligence-Backed Architecture: Leverages codebase analysis to inform tech stack selection, architectural patterns, and integration points, ensuring consistency and best practices.
  • Comprehensive Artifact Generation: Produces plan.md, research.md, data-model.md, contracts/, and quickstart.md for a complete technical blueprint.
  • Use Case: You have a clear feature specification and need to define how to build it. Use this Skill to generate a full technical implementation plan, including architectural decisions, data models, API contracts, and test scenarios, all validated against your project's constitutional principles.

Quick Start

To create an implementation plan from an existing specification:

Ensure your spec.md is in specs/<feature-id>/spec.md

Then, simply invoke the skill:

/plan specs/my-feature/spec.md

Frequently Asked Questions about Implementation Planning

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

FAQPage Schema
How do I turn a feature specification into a technical implementation plan?▼

Implementation planning transforms specifications into concrete technical blueprints by analyzing requirements and generating architectural decisions, data models, API contracts, and deployment strategies. Place your spec.md in specs/<feature-id>/ and invoke /plan specs/<feature-id>/spec.md to produce plan.md, research.md, data-model.md, contracts/, and quickstart.md artifacts.

What's included in a technical implementation plan?▼

A complete plan includes architecture design decisions backed by codebase analysis, data modeling documentation, API contract specifications, constitutional compliance validation against complexity gates, and executable quickstart guidance. All artifacts integrate with downstream workflows like generate-tasks and /implement for end-to-end delivery.

How does constitutional gatekeeping work in implementation planning?▼

Constitutional gates validate technical designs against predefined project constraints—such as maximum abstraction layers or project scope limits—both before finalizing architecture and after design completion. This prevents costly rework and ensures all implementation decisions comply with your project's established principles.

Can I use implementation planning without a formal specification document?▼

No. Implementation planning requires an existing specification to generate a technical plan. The skill bridges specifications to architecture; if you lack a spec, create one first to define feature requirements, scope, and acceptance criteria before planning implementation.

What tech stacks and architectural patterns does implementation planning support?▼

The skill analyzes your codebase to recommend tech stacks and patterns consistent with your existing project. It supports any architecture pattern your dependencies enable—whether microservices, monolithic, event-driven, or other approaches—and generates integration guidance specific to your stack.

How does implementation planning integrate with build and deployment workflows?▼

Generated artifacts feed directly into automated workflows: plan.md and contracts/ inform generate-tasks for ticket creation, /audit validates compliance, and /implement executes the plan. This ensures technical decisions flow seamlessly from planning through execution and testing.

Related Skills

Explore More Software Engineering Skills→
lionbenjaminlionbenjamin
15

specify

Draft product specifications with problem, goals, user stories, and acceptance criteria.

Community
Intermediate
cookeyholdercookeyholder

openspec-propose

Generate OpenSpec change proposals with design and task artifacts.

Community
Advanced
giovannimnzgiovannimnz

gsd-map-codebase

Generate a .planning/codebase-map.md detailing structure, dependencies, and integration points.

Community
Intermediate
robit-manrobit-man

tot-exploration

Generate and evaluate architectural alternatives to produce Architecture Decision Records.

Community
Advanced