cothought:begin-project

Initialize a GitHub repository from a project idea note with docs and context.

7|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/elliotbonneville/claude-cothought --skill cothought-begin-project
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cothought:begin-project
Source: https://github.com/elliotbonneville/claude-cothought/tree/main/skills/begin-project
Command: npx skills add https://github.com/elliotbonneville/claude-cothought --skill cothought-begin-project

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Spin up a new project repo from a project idea note in the notes directory. This is the execution phase — the project note should already exist (created by /cothought:project). If it doesn't, create one first or point the user to /cothought:project.

Core Features & Use Cases

  • Create a new repository structure under the configured dev_dir/category and initialize it with git.
  • Copy the project note into the repo as docs/RESEARCH.md and link related zettelkasten notes to preserve context.
  • Create a minimal README and commit history to seed the remote GitHub repo.
  • Update the zettelkasten note network to reflect the spun-up repository and backlinks.

Quick Start

Run /cothought:begin-project after selecting a project idea to spin up the repository.

Frequently Asked Questions about cothought:begin-project

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

FAQPage Schema
How do I automatically create a GitHub repository from a markdown project note?

To create a GitHub repository from a markdown project note, this Skill automates initializing the repo, copying the note as documentation, linking related zettelkasten notes, and pushing an initial commit to GitHub.

How do I start a new git repository and preserve my zettelkasten notes as context?

Starting a new git repository while preserving zettelkasten notes is handled by copying your project idea note into the repo as docs/RESEARCH.md and updating the note network to reflect the new repository backlinks.

Can I configure custom directory paths when automating GitHub repo creation from a project idea?

You can configure custom directory paths for automating GitHub repo creation by setting config-driven paths for notes_dir, dev_dir, and dev_categories to control where notes are stored and where the repository is initialized.

What do I need before spinning up a new project repo from a notes-based idea?

Before spinning up a new project repo, you need an existing project idea note in your notes directory and Git with GitHub tooling configured to allow the Skill to create and push the initial repository structure.

Does this project initialization tool create the initial project idea note for me?

This project initialization tool does not create the initial project idea note; it is designed as the execution phase that spins up the repository from an existing note, so you must create the project note first.

What's the best way to seed a new GitHub repo with documentation and an initial commit?

The best way to seed a new GitHub repo with documentation and an initial commit is to automate the creation of a minimal README, copy your project note as research docs, and push the initial commit structure to the remote repository.