Can it suggest a tech stack if I am unsure?

Yes, if you have no preference, the skill can propose a recommended stack based on your project's unique requirements and briefly explain the trade-offs of each choice.

Where is the blueprint document stored?

By default, the skill writes the final output to docs/implementation-blueprint.md within your project repository, though you can specify a different location.

What is an Implementation Blueprint?

An Implementation Blueprint is a technical companion to a project specification that defines the 'how' of a project, including specific frameworks, libraries, and folder structures.

How does this skill differ from a regular specification?

A specification defines the functional requirements ('what to build'), while the blueprint defines implementation details ('how to build it'), such as choosing React over Vue or SQLite over PostgreSQL.

Is the output compatible with other AI agents?

Absolutely; the generated blueprint is specifically designed to give any developer or AI agent the exact context and dependency list needed to scaffold and build the project.

Implementation Blueprint

Name: Implementation Blueprint
Author: ichabodcole

byichabodcole

0•

Learning & Documentation

Bridges the gap between project specifications and code by generating detailed technical implementation plans through structured user interviews.

This skill streamlines the transition from product requirements to actual development by analyzing technology-agnostic specifications and conducting a targeted technical discovery process. It guides users through critical decisions regarding tech stacks, platform targets, data layers, and development environments, ultimately producing a comprehensive implementation-blueprint.md file. This document serves as a definitive guide for AI agents or human developers, providing specific versioned dependencies, architectural patterns, and directory structures needed to begin building immediately.

Key Features

01Mapping of functional specification domains to implementation modules and directories

02Generation of a standardized blueprint with pinned versions and specific library choices

03Automated analysis of specification documents to identify required technical decisions

04Structured multi-round interview process covering platforms, UI, data, and dev environments

05Proactive technical recommendations with brief trade-off analysis for undecided users

060 GitHub stars

Use Cases

01Moving from a high-level product specification to a concrete, buildable technical architecture

02Standardizing project structure and technology choices for a new repository or team

03Performing technical discovery to identify dependencies and risks before implementation begins

Key Features

01Mapping of functional specification domains to implementation modules and directories

02Generation of a standardized blueprint with pinned versions and specific library choices

03Automated analysis of specification documents to identify required technical decisions

04Structured multi-round interview process covering platforms, UI, data, and dev environments

05Proactive technical recommendations with brief trade-off analysis for undecided users

060 GitHub stars

Use Cases

01Moving from a high-level product specification to a concrete, buildable technical architecture

02Standardizing project structure and technology choices for a new repository or team

03Performing technical discovery to identify dependencies and risks before implementation begins