wf-docker-genesis-bootstrap-method

Convert unclear project intent into a canonical package via a structured no-code Genesis workflow.

Updated Nov 7, 2025
One-click install
npx skills add https://github.com/belluga/delphi-ai --skill wf-docker-genesis-bootstrap-method
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wf-docker-genesis-bootstrap-method
Source: https://github.com/belluga/delphi-ai/tree/main/.cline/skills/wf-docker-genesis-bootstrap-method
Command: npx skills add https://github.com/belluga/delphi-ai --skill wf-docker-genesis-bootstrap-method

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This workflow provides a disciplined no-code path to transform unclear project intent into a first canonical package, preventing premature tactical implementation and preserving governance over the notion-to-build transition.

Core Features & Use Cases

  • Structured Genesis workflow to capture decisions, gaps, and next interview fronts, ensuring traceability and auditable reasoning.
  • Promotion of canonical docs such as project_constitution.md, system_roadmap.md, and foundation_documentation artifacts as interview truths stabilize.
  • Optional bootstrap packet generation to snapshot the project state for handoff and governance reviews.

Quick Start

Initiate Genesis / Product-Bootstrap by creating or updating the active Genesis capped TODO under foundation_documentation/todos/active/ to capture the current phase and next steps.

Frequently Asked Questions about wf-docker-genesis-bootstrap-method

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

FAQPage Schema
How do I bootstrap a project from unclear intent without writing code prematurely?

Project bootstrap is handled by a structured no-code workflow that converts unclear intent into a canonical package, capturing decisions and gaps while avoiding premature tactical implementation.

What is a Genesis capped TODO and how does it manage product inception?

A Genesis capped TODO is a live ledger under foundation_documentation/todos/active/ that tracks project phase, decisions, gaps, and next interview fronts during product inception and business-foundation refinement.

How do I create canonical project documentation during business-foundation refinement?

Canonical documents such as project_constitution.md, system_roadmap.md, and module contracts are promoted automatically as interview truths stabilize during the structured Genesis workflow.

Can I generate a snapshot of my project state for governance reviews during bootstrap?

Optional bootstrap packets are generated under foundation_documentation/artifacts/** to snapshot the project state, enabling governance reviews and handoff during the notion-to-build transition.

Does this Genesis workflow require any specific dependencies or prior setup?

No dependencies are required to run the Genesis workflow; you initiate it by creating or updating the active Genesis capped TODO to capture the current phase and next steps.

When should I avoid using a no-code bootstrap approach for project documentation?

This no-code bootstrap approach is designed for inception and business-foundation refinement; it should be avoided when the project requires immediate tactical implementation rather than governance over the notion-to-build transition.