A command for starting a new software project by discussing its requirements, writing a specification, creating a GitHub repository, and planning work as issues. It stops before writing implementation code.

Use it when beginning a project that needs a requirements discussion, README, repository, specification, and implementation plan.

It separates planning from coding, so the project has a written plan and organized tasks that can be continued later or handed to another coding session.

project-new — Command for Claude Code by thrashr888

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo

git clone --depth 1 https://github.com/thrashr888/AllBeads

Made for: Claude Code.

Or install allbeads, the plugin that ships this one along with the rest of its 1 skill, 19 commands, 1 hook.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/thrashr888/allbeads/project-new/github.svg)](https://agentmods.dev/commands/thrashr888/allbeads/project-new)

Your own site

<a href="https://agentmods.dev/commands/thrashr888/allbeads/project-new"><img src="https://agentmods.dev/badge/commands/thrashr888/allbeads/project-new/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/thrashr888/allbeads/project-new"><img src="https://agentmods.dev/badge/commands/thrashr888/allbeads/project-new.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 751 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00014	$0.00751
Opus 5	$0.00007	$0.00376
Sonnet 5	$0.00003	$0.00150
Haiku 4.5	$0.00001	$0.00075

Measured 8d ago against content hash 128feec9b90e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

project-new scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude-plugin/commands/project-new.md · 92 lines

How it starts

The opening of the file, as written. The whole thing — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Create a new GitHub repository with AllBeads and plan the work using beads issues. Does not write code - just sets up the project structure and creates the implementation plan.

Workflow

Gather Requirements - Discuss the project idea with the user
Create Spec - Write a detailed specification document
Create Repo - Use ab context new to create GitHub repo
Create README - Add README.md with project overview and status
Create Beads - Create epic issues with specs embedded in descriptions
STOP - Do not write implementation code

The implementation will be handled later by:

User manually starting work
/handoff workflow (ab-vlq) triggering agent work
Another session picking up from bd ready

Why This Workflow?

Separation of Concerns - Planning and implementation are distinct phases
Better Handoffs - Beads contain all context needed for implementation
Interruptible - Work can be picked up across sessions
Agent-Friendly - Any agent can implement from the beads

Usage

When the user describes a new project idea:

Ask clarifying questions about requirements
Write a spec document (can be in AllBeads/specs/ or in the new repo)

Create the repo:

ab context new <project-name> --private --gitignore <lang> --license <license>

Create README.md with:
- Project overview
- Status: "Planning Phase"
- Planned features table
- Example usage (planned)

Create beads epics for each phase:

bd create --title="[Phase 1] ..." --type=epic --priority=1

Add detailed descriptions to beads (specs, requirements, acceptance criteria)

What NOT to Do

Do NOT create source code files
Do NOT set up build/test infrastructure
Do NOT create CI/CD pipelines
Do NOT implement any features

All implementation should wait for the handoff workflow or explicit user request.

Example Session

User: I want to build a CLI tool that converts markdown to PDF

Agent: Great idea! Let me ask some questions:
- What language? (Go, Rust, Python?)
- Should it support themes/styles?
- Any specific PDF features (TOC, headers/footers)?

User: Go, yes to themes, and TOC would be nice

Agent: Perfect. Let me plan this project...

1. Creating spec document...
2. Creating repo with `ab context new md2pdf --private --gitignore Go --license MIT`
3. Adding README.md with project overview
4. Creating beads:
   - [Phase 1] Core CLI structure
   - [Phase 2] Markdown parsing
   - [Phase 3] PDF generation
   - [Phase 4] Theme support
   - [Phase 5] TOC generation

Project planned! The beads contain full specs. Implementation can begin via:
- `bd ready` to see available work
- `/handoff` to trigger agent implementation
- Or start manually: `bd update md2pdf-xxx --status=in_progress`

Read the full file on GitHub · 92 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

8d ago First seen · 92 lines · 14 tokens per session scan A 128feec9b90e

Subscribe to this mod's changes

project-new is a command published in the GitHub repository thrashr888/AllBeads (8 stars, last pushed 9d ago), licensed MIT. It adds 14 tokens to every session and 751 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Planning Project Management Project management beads issues jira

project-new

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Workflow

Why This Workflow?

Usage

What NOT to Do

Example Session

What this file has done since we first saw it

Other commands, from other repositories

pm-done

pm-status

pm-charter

pm-check

_closing

jira-discover-project