blueprint

Generate implementation blueprints with task lists and dependency checks from design documents.

2|Updated Jun 18, 2026
One-click install
npx skills add https://github.com/bllshttng/footnote --skill blueprint-bllshttng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: blueprint
Source: https://github.com/bllshttng/footnote/tree/main/skills/blueprint
Command: npx skills add https://github.com/bllshttng/footnote --skill blueprint-bllshttng

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps software project teams create detailed implementation blueprints (plans) to ensure a structured approach to development and reduce miscommunication.

Core Features & Use Cases

  • Implementation Blueprints: Generate detailed plans for software features, including design considerations, tasks, and dependencies.
  • Input Flexibility: Accepts both design document paths and raw feature descriptions as input.
  • Use Case: You can use this Skill to outline the implementation steps for a new feature, based on an existing design document or a high-level feature description.

Quick Start

To create a plan, use the command: /blueprint "add OAuth login".

Frequently Asked Questions about blueprint

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

FAQPage Schema
How do I generate an implementation blueprint for a software project?

You generate an implementation blueprint by providing a design document path or raw feature description, allowing the skill to parse inputs and automate task lists, dependency checks, and planning elements.

Can I create software development plans from just a feature description?

Yes, you can create software development plans from raw feature descriptions, as the skill accepts both design document paths and high-level text inputs to outline implementation steps.

Do I need the fno library to parse design documents into task lists?

Yes, the fno library is required for backend processing and interaction with project management tools to parse design documents and generate detailed task lists.

What's the best way to outline implementation steps for a new feature?

The best way to outline implementation steps is using a dedicated command to parse feature descriptions, automatically generating design considerations, tasks, and dependency checks.

Are there limitations when automating dependency checks for software plans?

Automating dependency checks requires the fno library for backend processing, meaning functionality is constrained by library support and available project management tool interactions.