development

Coordinate planning, beads tracking, and governance across AllBeads repositories.

8|1|Updated Jan 9, 2026
One-click install
npx skills add https://github.com/thrashr888/AllBeads --skill development-thrashr888
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: development
Source: https://github.com/thrashr888/AllBeads/tree/main/.claude/skills/development
Command: npx skills add https://github.com/thrashr888/AllBeads --skill development-thrashr888

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

AllBeads development guidance consolidates planning, governance, and documentation workflows across multiple repositories, enabling teams to coordinate beads, specs, and skills effectively.

Core Features & Use Cases

  • Outline of the 5-Style Documentation System (Plan Mode, Beads, Evergreen Specs, Skills, and User Docs) and how plans are preserved to support cross-repo collaboration.
  • Step-by-step workflow from idea to code, including EnterPlanMode, plan creation, beads management, spec/skill updates, implementation, and quality gates.
  • Beads essentials and governance workflows for multi-session work, tracking status, dependencies, and synchronization with external trackers.

Quick Start

Enter Plan Mode, read relevant specs, write an initial plan to plans/, and begin tracking work with beads.

Frequently Asked Questions about development

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I coordinate planning and issue tracking across multiple repositories?

Multi-repo development coordination is managed by consolidating planning, governance, and documentation workflows. This enables teams to track beads, specs, and skills effectively across member repositories.

What is the plan-mode workflow for feature development?

Plan-mode workflow involves entering Plan Mode, reading relevant specs, writing an initial plan to the plans directory, and tracking work with beads. It spans idea to code including implementation and quality gates.

How do I manage beads for multi-session development work?

Beads management for multi-session work involves tracking status, dependencies, and synchronizing with external trackers. Governance workflows ensure beads are properly maintained across sessions.

What documentation system does AllBeads development use?

The 5-Style Documentation System consists of Plan Mode, Beads, Evergreen Specs, Skills, and User Docs. Plans are preserved to support cross-repo collaboration.

Can I use this for architectural changes across member repositories?

Yes, this approach is applied to architectural changes across member repositories. It satisfies requirements for plan-mode workflows, beads issue management, spec and skill updates, and automated quality gates.

What's the best way to start end-to-end development with beads tracking?

To start end-to-end development, enter Plan Mode, read relevant specs, write an initial plan to the plans directory, and begin tracking work with beads. Quality gates validate the implementation.