Project Setup Workflow

Bootstrap Mycelium projects by detecting state and creating .workflow structure.

Updated Feb 3, 2026
One-click install
npx skills add https://github.com/jason-hchsieh/mycelium --skill project-setup-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Project Setup Workflow
Source: https://github.com/jason-hchsieh/mycelium/tree/main/skills/workflow/setup
Command: npx skills add https://github.com/jason-hchsieh/mycelium --skill project-setup-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the startup of a Mycelium project, removing guesswork and ensuring a standardized workspace with a ready .workflow folder, quick context files, and a mandatory Git repository.

Core Features & Use Cases

  • Detects whether a project is new (greenfield) or existing (brownfield) and bootstraps the appropriate structure.
  • Creates the .workflow/ directory structure, including context files under .workflow/context (product.md, tech-stack.md, workflow.md).
  • Initializes a Git repository and applies a .gitignore tailored for the detected tech stack.
  • Supports resumable progress by saving state after each interaction and enforcing a mandatory Git setup during initialization.

Quick Start

Run the interactive setup at the project root to bootstrap the .workflow structure and initialize a mandatory Git repository.

Frequently Asked Questions about Project Setup Workflow

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

FAQPage Schema
How do I bootstrap a Mycelium project and set up the required Git workflow structure?

To bootstrap a Mycelium project, run the interactive setup at the project root. It detects the project state, creates the .workflow directory structure with context files, and initializes a mandatory Git repository with a tailored .gitignore.

What is the best way to scaffold a .workflow context structure for an existing codebase?

For existing codebases, the setup detects the brownfield state and bootstraps the appropriate .workflow structure. It generates context files like product.md, tech-stack.md, and workflow.md while applying a .gitignore tailored to the detected tech stack.

Can I resume a Mycelium project setup if the initialization process is interrupted?

Yes, the Mycelium project setup supports resumable progress by saving its state after each interaction. You can safely resume the workflow scaffolding and mandatory Git initialization without losing prior configuration steps.

Does the project bootstrapping process require a pre-existing Git repository?

No, a pre-existing Git repository is not required because the setup enforces a mandatory Git initialization during the process. It automatically initializes the repository and applies the necessary .gitignore for your detected tech stack.

Why do I need a .workflow directory structure for my project setup?

The .workflow directory provides a standardized workspace by storing context files such as product.md, tech-stack.md, and workflow.md. This removes guesswork and ensures consistent project orchestration across greenfield and brownfield scenarios.

What is the difference between greenfield and brownfield project bootstrapping in this workflow?

Greenfield bootstrapping initializes a completely new Mycelium project structure, while brownfield bootstrapping detects an existing project state and applies the .workflow scaffolding and Git setup without disrupting the current codebase.