ワンクリックでManusで任意のスキルを実行

greenfield-bootstrap

スター41

フォーク8

更新日2026年7月6日 11:07

Bootstrap repo-local governance before CC_GodMode workflows run in an empty, newly initialized, or undocumented workspace. Use proactively when a project has no CLAUDE.md, no README, or no clear structure yet.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

cubetribe

cubetribe/ClaudeCode_GodMode-On

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

Greenfield Bootstrap

Use this skill before the normal workflows pipeline when the current workspace is empty, newly initialized, or missing the local governance needed for safe multi-step implementation. It establishes just enough structure that @architect and @builder have firm ground to stand on.

Required outcome

a minimal, truthful repo-local constitution before feature work starts
structure that is tied to the actual project, not an invented one
small enough that it can realistically stay maintained

Default route

Inspect the workspace and confirm what already exists (files, language, package manager, VCS state). Do not assume.
Create the smallest governance surface needed:
- a project CLAUDE.md (copy ~/.claude/templates/CLAUDE-ORCHESTRATOR.md and trim to the project) so the Orchestrator and agents have rules
- a basic README.md with purpose + how to run, if none exists
- a VERSION file (start at 0.1.0) as the single source of truth for the project version (written only by release sprints, ADR-004)
- validation and release notes for the touched scope (how tests run, how releases are cut — even if "none yet")
Make structure explicit — where source, config, tests, and docs belong.
Hand off — once the constitution exists, continue under the normal workflows pipeline (@architect first for any real feature).

Core rules

Do not invent architecture the project has not chosen yet — record decisions as they are made via @architect, not preemptively.
Prefer durable markdown guidance over chat-only agreements.
Keep initial rules short enough to stay maintained.
Still honor CC_GodMode core rules: plan-first (ADR-004), never push without permission, delegate via the Task tool.

Hand-off targets

After bootstrap	Use
First real feature	`workflows` → Feature workflow (`@architect` → `@builder` → gates)
Security-sensitive scaffolding	route gates through `@security`
Throwaway spike instead	`prototype-mode` skill

Do not use when

the workspace already has clear local governance (CLAUDE.md + structure)
the task is only a one-off answer with no lasting repo changes

このリポジトリの他の Skills

同じリポジトリ

dynamic-workflows

cubetribe/ClaudeCode_GodMode-On

Ultracode / Max-Parallel mode — dynamic workflows fan work out across tens–hundreds of adversarially-verified parallel subagents for large, decomposable jobs (codebase-wide audits, big migrations, cross-checked research). Opt-in; higher token spend.

2026-07-0641

cost-efficiency

cubetribe/ClaudeCode_GodMode-On

Smart Routing — the DEFAULT CC_GodMode routing policy. Risk-based, minimal-agent paths that preserve required safety gates for the changed scope.

2026-07-0641

release

cubetribe/ClaudeCode_GodMode-On

Release sprint workflow: version-at-release via tooling, CHANGELOG [Unreleased] flow, release invariant checks, tags, GitHub Releases, RCs. Authoritative law: docs/orchestrator/VERSIONING.md

2026-07-0641

sprint-planning

cubetribe/ClaudeCode_GodMode-On

Plan-first orchestration (ADR-004): comprehensive PLAN.md, sprint files with write-scope ownership, preflight checks, serialized integration, and the release sprint. Use for any non-trivial or multi-part request BEFORE dispatching agents.

2026-07-0641

departments

cubetribe/ClaudeCode_GodMode-On

Expanded department-based orchestration for large cross-domain CC_GodMode work. Freezes ownership, handoffs, and write scopes before implementation.

2026-07-0641

meta-decisions

cubetribe/ClaudeCode_GodMode-On

Meta-decision logic that adapts workflows based on task analysis — security overrides, breaking change escalation, performance paths, emergency hotfix, and documentation optimization

2026-07-0641

Greenfield Bootstrap

Required outcome

a minimal, truthful repo-local constitution before feature work starts

structure that is tied to the actual project, not an invented one

small enough that it can realistically stay maintained

Default route

Inspect the workspace and confirm what already exists (files, language, package manager, VCS state). Do not assume.

Create the smallest governance surface needed:

a project CLAUDE.md (copy ~/.claude/templates/CLAUDE-ORCHESTRATOR.md and trim to the project) so the Orchestrator and agents have rules
a basic README.md with purpose + how to run, if none exists
a VERSION file (start at 0.1.0) as the single source of truth for the project version (written only by release sprints, ADR-004)
validation and release notes for the touched scope (how tests run, how releases are cut — even if "none yet")

Make structure explicit — where source, config, tests, and docs belong.

Hand off — once the constitution exists, continue under the normal workflows pipeline (@architect first for any real feature).

Core rules

Do not invent architecture the project has not chosen yet — record decisions as they are made via @architect, not preemptively.

Prefer durable markdown guidance over chat-only agreements.

Keep initial rules short enough to stay maintained.

Still honor CC_GodMode core rules: plan-first (ADR-004), never push without permission, delegate via the Task tool.

Hand-off targets

After bootstrap

Use

First real feature

workflows → Feature workflow (@architect → @builder → gates)

Security-sensitive scaffolding

route gates through @security

Throwaway spike instead

prototype-mode skill

Do not use when

the workspace already has clear local governance (CLAUDE.md + structure)

the task is only a one-off answer with no lasting repo changes

name	greenfield-bootstrap
description	Bootstrap repo-local governance before CC_GodMode workflows run in an empty, newly initialized, or undocumented workspace. Use proactively when a project has no CLAUDE.md, no README, or no clear structure yet.