bead-implementation

Enforce bead session discovery and mandatory git push before close.

1|Updated Jan 7, 2026

Search Tags:#workflow #discovery #session-management #follow-up #issue-tracking #bead #git-push

Ready to run

npx skills add https://github.com/moogah/claude_skills --skill bead-implementation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bead-implementation
Source: https://github.com/moogah/claude_skills/tree/main/bead-implementation
Command: npx skills add https://github.com/moogah/claude_skills --skill bead-implementation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bead-driven workflows require disciplined discovery and strict session closure to ensure work is traceable and committed. This skill provides a repeatable process to keep a single bead focused and ensure changes are pushed before completion.

Core Features & Use Cases

Enforces "one bead per session" rule and mandatory push.
Supports creating follow-up beads for discovered work externalization.
Provides a session close protocol with seven steps to finalize work and hand off context.

Quick Start

Start a new bead session with a narrowly scoped task, claim it as in_progress, and complete the session by pushing changes and closing the bead.

Frequently Asked Questions about bead-implementation

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

FAQPage Schema

How do I enforce a mandatory git push before closing a development session?▼

To enforce a mandatory git push before closing a development session, this workflow uses a strict session-close protocol that requires the push to complete before finalizing work and handing off context. It guarantees changes are committed and traceable.

What is the best way to manage discovered work without losing focus on the current task?▼

To manage discovered work without losing focus, you can create follow-up beads via standardized commands. This externalizes new issues into separate sessions, ensuring your current bead remains narrowly scoped and disciplined.

How does a bead workflow handle session management and issue tracking?▼

A bead workflow handles session management and issue tracking by enforcing a one bead per session rule. It orchestrates discovery, tracks the session as in_progress, and requires a seven-step close protocol to finalize the work.

Can I start a new task without completing the seven-step session close protocol?▼

You cannot start a new task without completing the seven-step session close protocol. The workflow enforces strict session closure, requiring a guaranteed git push and handoff before you can claim a new bead as in_progress.

Do I need to manually push my changes when the session closes?▼

You do not need to manually push changes when the session closes, as the workflow enforces a guaranteed push during its close protocol. The session close process handles the git push automatically to ensure work is committed.