Keysat
8548afd9fd
The inverse of /retrofit: workshops a captured (new) inbox idea into a repo that is standards-compliant from line one (AGENTS.md + CLAUDE.md symlink, ROADMAP, canonical deny-by-default .gitignore, .claude wiring, inbox-check line), publishes via a manual Gitea-create gate, and clears the (new) inbox item. Resolves ROADMAP item 5 open questions (manual Gitea gate; stack quality gate deferred to /harden; workshop seeds Current state) and marks it BUILT.
1.2 KiB
description, argument-hint, allowed-tools
| description | argument-hint | allowed-tools | ||||
|---|---|---|---|---|---|---|
| New-project bootstrap — workshop a captured idea into a standards-compliant repo (AGENTS.md + symlink, ROADMAP, canonical .gitignore, .claude wiring) and publish it to Gitea |
|
Bash, Read, Edit, Write, Grep, Glob, Agent |
Bootstrap a brand-new project under ~/Projects, standards-compliant from line one.
Optional seed from me (may be empty): $ARGUMENTS
Your complete orchestration guide — locating the inbox seed, the scope workshop, the sign-off gate, the scaffold layout, the Gitea publish step, and the final report — is at:
~/Projects/standards/guides/new-project.md
Read it in full first, then follow it exactly. If you cannot read that file, stop and report precisely that — do not improvise the bootstrap.
This runs in the main thread on purpose: scoping a new project is a conversation. Ask me the judgment calls (the objective and non-goals, the stack, the architectural forks, the scaffolding-plan sign-off, and the Gitea publish) and wait — nothing lands on disk before Phase 3, and nothing is created without my sign-off in Phase 2. My remote is self-hosted Gitea, never GitHub.