lambda-workflow

Automate Lambda repository delivery from task selection through PR merge.

2|Updated Nov 11, 2025
One-click install
npx skills add https://github.com/lambdamechanic/sk --skill lambda-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lambda-workflow
Source: https://github.com/lambdamechanic/sk/tree/main/skills/lambda-workflow
Command: npx skills add https://github.com/lambdamechanic/sk --skill lambda-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a standardized, efficient, and observable development workflow, eliminating manual overhead and inconsistencies from task selection to PR merge. It ensures every step is tracked, validated, and automated where possible.

Core Features & Use Cases

  • Task Management: Guides on selecting and claiming bd (beads) tasks, ensuring clear ownership, dependency tracking, and immediate updates to the shared task database.
  • PR Automation: Facilitates the creation of draft PRs, continuous integration with frequent commits, and preparation for review with automated quality gates and rebase instructions.
  • Automated Monitoring: Integrates with the Dumbwaiter MCP to automatically monitor GitHub PR status, CI checks, reviews, and merges, eliminating manual polling.
  • Use Case: An AI agent needs to take a new development task from inception to completion. This skill provides the end-to-end instructions, from claiming a bd issue and opening a draft PR, to monitoring its merge status via Dumbwaiter MCP.

Quick Start

Guide me through the process of selecting an unblocked bd task, claiming it, and then opening a draft GitHub PR for a new feature branch.

Frequently Asked Questions about lambda-workflow

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

FAQPage Schema
How do I automate my development workflow from task selection to PR merge?

Automating end-to-end development workflows involves orchestrating task selection, drafting PRs, running CI checks, and monitoring merge status. This Skill guides you through claiming bd issues, creating draft PRs, enforcing tests-first development, and using Dumbwaiter MCP to automatically track GitHub status until merge, eliminating manual overhead.

Can I integrate GitHub PR management with automated CI/CD monitoring?

Yes. This workflow integrates GitHub PR creation with continuous integration checks and automated monitoring via Dumbwaiter MCP. It tracks CI results, review signals, and merge readiness automatically, syncing state back to bd issues so you see the complete picture without manual polling.

How do I claim a bd task and open a draft PR for a feature branch?

Select an unblocked bd issue, claim ownership to update the shared task database, create a feature branch with proper naming discipline, open a draft PR, and commit frequently with tests-first development. The workflow then handles continuous integration and prepares the PR for review with automated quality gates.

What's required before starting end-to-end task automation in a Lambda project?

Your repository must use bd issues for task tracking, support draft PRs, have CI checks configured, and integrate Dumbwaiter MCP for monitoring. The workflow enforces baseline setup and repo hygiene, so ensure these foundations exist before claiming work.

Does this workflow enforce specific branching and testing discipline?

Yes. It enforces baseline setup, tests-first development, branching discipline, and acceptance criteria capture. Every step is tracked with traceability by updating issues and syncing state, ensuring consistent repo hygiene and merge readiness across the team.

Why use automated monitoring instead of manual PR status checks?

Automated monitoring via Dumbwaiter MCP eliminates manual polling, reduces context-switching, and ensures you catch CI failures, review blockers, and merge signals immediately. This keeps work flowing and prevents PRs from stalling between development and landing.