beans

Coordinate bean creation, status updates, and relationships in VS Code workspaces.

Updated Oct 22, 2021
One-click install
npx skills add https://github.com/open-ortho/lectures --skill beans
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: beans
Source: https://github.com/open-ortho/lectures/tree/main/.agents/skills/beans-vscode
Command: npx skills add https://github.com/open-ortho/lectures --skill beans

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a guided, centralized workflow to manage Beans inside a VS Code workspace, replacing ad-hoc todos with a structured, consistent bean lifecycle.

Core Features & Use Cases

  • Centralizes bean tracking in the VS Code environment, enabling quick creation and lookup of beans.
  • Manages bean attributes (status, type, priority, parent, blocking/blocked-by relationships) and keeps them synchronized with code changes.
  • Maintains a live ## Todo checklist in the bean body and guides epic decomposition to create focused child beans.
  • Guides branch naming via Git Flow mapping and records branch and PR details in the bean frontmatter.
  • Encourages using the Beans extension commands or MCP tools over manual work, improving reproducibility and traceability.

Quick Start

Open the Beans workspace, locate or create a bean, and start updating its fields and Todo list to reflect current work.

Frequently Asked Questions about beans

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

FAQPage Schema
How do I manage issue tracking and task workflows directly inside VS Code?

You can manage issue tracking inside VS Code by using a structured bean lifecycle to create, update, and link tasks. This replaces ad-hoc todos by centralizing status, priority, and parent-child relationships within your workspace.

What is the best way to decompose epics into focused child tasks in a Git Flow environment?

Epic decomposition in a Git Flow environment is best handled by guiding the creation of focused child beans. This process breaks down large epics into manageable tasks while automatically suggesting branch naming conventions to keep code synchronized.

How do I keep my task checklists and frontmatter synchronized with code changes?

To keep task checklists and frontmatter synchronized with code changes, maintain a live Todo list in the bean body. The workflow enforces commit discipline by automatically recording branch and PR details directly in the bean frontmatter.

Can I use VS Code workspace commands instead of manual edits for task management?

Yes, you can use Beans extension commands or MCP tools instead of manual edits for task management. This approach improves reproducibility and traceability when updating bean status, type, priority, or blocking relationships.

Does this workflow approach support tracking blocked-by and blocking relationships for issues?

Yes, this workflow approach fully supports tracking blocked-by and blocking relationships for issues. It manages bean attributes including status, type, priority, and parent links to maintain clear dependency maps across your workspace.