Skip to content
Back to skills

Cocobrew

ASecurity

Enter the Build phase of CocoBrew. Reads plan.md, invokes CocoHarvest to decompose the plan into parallel workstreams, assigns personas, generates flow.json stages, and begins execution via $flow run. Must have $plan completed and approved first.

  • 724 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added June 5, 2026
ai-agentsgit

Security analysis

A100/100

Pro scans all 8 files and shows the line behind each finding

Scanned June 5, 2026

npx -y skills add Snowflake-Labs/cocoplus --skill cocobrew --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Cocobrew?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Cocobrew
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/snowflake-labs-cocobrew/badge)](https://www.skillsdirectory.com/skills/snowflake-labs-cocobrew)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: "build"
description: "Enter the Build phase of CocoBrew. Reads plan.md, invokes CocoHarvest to decompose the plan into parallel workstreams, assigns personas, generates flow.json stages, and begins execution via $flow run. Must have $plan completed and approved first."
version: "1.0.1"
author: "CocoPlus"
tags:
  - cocoplus
  - lifecycle-engine
---

You are executing the Build phase (3/6) of CocoBrew. Your objective is to transform the approved plan into executing workstreams.

Before proceeding, verify that `.cocoplus/` exists in the current directory.
If it does not, output: "CocoPlus not initialized in this directory. Run `$pod init` to begin." Then stop.

Read `.cocoplus/lifecycle/meta.json`. Verify `phases_completed` contains both `"spec"` and `"plan"`.
If not: output "The Spec and Plan phases must be completed before building. Check `$pod status` for current state." Then stop.

Verify that the artifact files actually exist on disk — meta.json alone is not sufficient:
- Check `.cocoplus/lifecycle/spec.md` exists. If not: output "spec.md is missing from `.cocoplus/lifecycle/`. The Spec phase record is incomplete. Re-run `$spec` to regenerate it." Then stop.
- Check `.cocoplus/lifecycle/plan.md` exists. If not: output "plan.md is missing from `.cocoplus/lifecycle/`. The Plan phase record is incomplete. Re-run `$plan` to regenerate it." Then stop.

## SecondEye Gate Check

Scan `.cocoplus/lifecycle/` for any files matching `secondeye-*.md`.
For each file found, check YAML frontmatter for `critical_open: true` and `acknowledged: false`.
If any such file exists:
- Output: "Unacknowledged critical findings from SecondEye review. Run `$secondeye acknowledge` to review and acknowledge before building."
- List the finding summaries.
- Stop.

## Complexity Assessment

Read `.cocoplus/lifecycle/plan.md`. Assess complexity:
- Count workstreams listed in the plan
- Identify if multiple personas are required
- Check if any stages have external dependencies

If 3 or more workstreams OR multiple personas required:
→ Complexity = HIGH → invoke CocoHarvest automatically

If fewer than 3 workstreams AND single persona sufficient:
→ Complexity = LOW → offer simple execution without CocoHarvest

Tell the developer the complexity assessment and proceed accordingly.

## Invoke CocoHarvest (for HIGH complexity)

Activate the `cocoharvest` skill to:
1. Decompose plan.md into parallel workstreams
2. Assign personas
3. Generate flow.json stages
4. Create per-stage prompt files in `.cocoplus/prompts/`

## Update Build State

Update `.cocoplus/lifecycle/meta.json` — add build to phases_completed.

Append to AGENTS.md (keep ≤200 lines):
```
Phase: Build (3/6)
Build started: [timestamp]
CocoHarvest: [invoked/skipped]
```

Create git commit:
```
git add .cocoplus/lifecycle/meta.json .cocoplus/AGENTS.md .cocoplus/flow.json
git commit -m "build: begin build phase — CocoHarvest pipeline initialized"
```

## Begin Execution

If HIGH complexity: Activate `flow-run` skill to begin pipeline execution.
If LOW complexity: Execute the plan directly using the appropriate persona.

Output: "Build phase initiated. Use `$flow status` to monitor pipeline progress."

## Anti-Rationalization

| Shortcut / Temptation | Why It Fails |
|-----------------------|--------------|
| Skip SecondEye gate check and proceed directly to build | Unacknowledged Critical findings represent unresolved risks — building on top of them silently buries problems |
| Always invoke CocoHarvest regardless of complexity | Low-complexity plans don't need full pipeline decomposition; over-engineering wastes tokens and adds unnecessary stages |
| Mark build as complete before flow-run finishes | Build phase is only complete when execution has started, not just when CocoHarvest generates flow.json |

## Exit Criteria

- [ ] `.cocoplus/lifecycle/meta.json` `phases_completed` array contains `"build"`
- [ ] `.cocoplus/flow.json` has non-empty `stages` array (for HIGH complexity) or execution is underway
- [ ] Git commit with message `build: begin build phase` exists in log
- [ ] No unacknowledged SecondEye files with `critical_open: true` exist in `.cocoplus/lifecycle/`

Files in this skill

  • build.skill.md4.1 KB
  • plan.skill.md6.9 KB
  • review.skill.md5.3 KB
  • ship.skill.md5.6 KB
  • spec.skill.md7.2 KB
  • test.skill.md3.1 KB
  • worktree-utils.md580 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.