pour

Name: pour
Availability: InStock
Author: chowderr

Create a multi-step Beads workflow by pouring a selected formula into linked, gated issues.

2|1|Updated Feb 14, 2026

Search Tags:#workflow automation #beads #project kickoff #client engagement #dry-run validation #human gates #release deployment

Ready to run

npx skills add https://github.com/hamchowderr/braynee --skill pour-hamchowderr

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pour
Source: https://github.com/hamchowderr/braynee/tree/main/skills/pour
Command: npx skills add https://github.com/hamchowderr/braynee --skill pour-hamchowderr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Brute-forcing repeated Beads issue creation is slow and error-prone, especially when work follows a consistent multi-step shape with required variables and human gates.

Core Features & Use Cases

Formula-driven workflow pouring: Converts a chosen formula into a linked, gated molecule of Beads issues in one command.
Interactive variable collection: Guides the user through required and optional formula vars via questions, reducing missing-field mistakes.
Safety via mandatory dry-run: Always performs a dry-run first, then pours for real only after confirmation.
Aftercare for execution: Produces issues compatible with existing Beads flows like readiness checks, claiming work, and resolving gates.
Common use cases: Starting an internal project, onboarding a new paid client engagement, or shipping a braynee plugin release.

Quick Start

Use the command: /braynee:pour engagement.

Frequently Asked Questions about pour

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

FAQPage Schema

How do I automate Beads workflow issue creation for a project kickoff?▼

To automate Beads workflow issue creation for a project kickoff, use a formula-driven pour command that converts a selected recipe into linked, gated issues with required variables collected interactively.

What is the best way to structure recurring client engagement workflows with human gates?▼

Structuring recurring client engagement workflows with human gates is best handled by pouring a predefined formula into a linked sequence of Beads issues, ensuring consistent structure and mandatory dry-run validation before deployment.

How do I collect variables for Beads workflow issues without missing fields?▼

To collect variables for Beads workflow issues without missing fields, the pour process guides you through interactive AskUserQuestion prompts, ensuring all required and optional formula variables are gathered before execution.

Does the Beads workflow pour process require confirmation before creating issues?▼

Yes, the Beads workflow pour process requires a mandatory dry-run confirmation to validate the structure and variables before actually pouring the linked issues into your project.

Can I use workflow pouring for braynee plugin release deployments?▼

Yes, you can use workflow pouring for braynee plugin release deployments by selecting the appropriate formula to generate a consistent, gated molecule of Beads issues tailored to your release process.

Why should I use formula-driven pouring instead of brute-forcing Beads issue creation?▼

You should use formula-driven pouring instead of brute-forcing Beads issue creation because brute-forcing repeated tasks is slow and error-prone, whereas pouring applies consistent structure, variable collection, and human gates automatically.