AllBeads Development Orchestrator FAQs

Question 1

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

Accepted Answer

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.

Question 2

How are issues tracked in the AllBeads system?

Accepted Answer

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.

Question 3

Does this skill handle code quality automatically?

Accepted Answer

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

Question 4

Who is responsible for closing issues and pushing code?

Accepted Answer

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.

Question 5

What is the difference between Specs and Skills?

Accepted Answer

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

AllBeads Development Orchestrator

Key Features

Use Cases

Key Features

Use Cases