What is the purpose of 'Plan Mode' in this skill?

Plan Mode is a structured phase for deep architectural exploration and design documentation that occurs before any code is written, ensuring design decisions are preserved in the repository.

How are issues tracked in the AllBeads system?

Issues are managed as 'Beads,' which are git-tracked files stored in the .beads/ directory, allowing task status and dependencies to persist across different development sessions.

Does this skill handle code quality automatically?

Yes, it enforces mandatory quality gates including cargo fmt, cargo clippy, and cargo test to ensure all code meets project standards before being committed.

Who is responsible for closing issues and pushing code?

Following a strict safety protocol, the agent implements and commits the code, but the human user is responsible for testing the work, pushing to remote, and closing the issues.

What is the difference between Specs and Skills?

Specs are declarative documents that define the 'evergreen truth' of how a system works, while Skills are prescriptive guides that provide code-focused 'how-to' instructions for implementation.

AllBeads Development Orchestrator

Name: AllBeads Development Orchestrator
Author: thrashr888

bythrashr888

•

生産性とワークフロー

Orchestrates the full software development lifecycle within the AllBeads architecture using structured planning, git-tracked issue management, and prescriptive documentation standards.

AllBeads Development Orchestrator

bythrashr888

•

生産性とワークフロー

Orchestrates the full software development lifecycle within the AllBeads architecture using structured planning, git-tracked issue management, and prescriptive documentation standards.

概要

The AllBeads Development Process skill provides Claude with a specialized framework for navigating multi-repo agent orchestration. It enforces a rigorous five-tier documentation system that separates architectural truth from implementation guidance. By leveraging 'Plan Mode' for deep exploration and 'Beads' for session-persistent issue tracking, this skill ensures that development remains organized, documented, and aligned with system specs. It is particularly useful for complex projects requiring high architectural integrity and consistent quality gates across multiple repositories.

主な機能

Git-tracked issue management using the Beads CLI system
Integrated Plan Mode for architectural design and decision preservation
Five-tier documentation hierarchy (Plans, Beads, Specs, Skills, and User Docs)
Standardized workflow from initial feature idea to verified implementation
Enforced quality gates including Cargo formatting, linting, and testing
1 GitHub stars

ユースケース

Maintaining evergreen system specifications and prescriptive implementation guides
Managing long-running development tasks across multiple AI agent sessions
Designing complex features that require multi-file architectural changes and exploration

概要

主な機能

Git-tracked issue management using the Beads CLI system
Integrated Plan Mode for architectural design and decision preservation
Five-tier documentation hierarchy (Plans, Beads, Specs, Skills, and User Docs)
Standardized workflow from initial feature idea to verified implementation
Enforced quality gates including Cargo formatting, linting, and testing
1 GitHub stars

ユースケース

Maintaining evergreen system specifications and prescriptive implementation guides
Managing long-running development tasks across multiple AI agent sessions
Designing complex features that require multi-file architectural changes and exploration