Pulse v2 — Governance-Aware Autonomous Development
Pulse v2 enhances autonomous development sessions with: - **Governance Integration** — Reads and updates project checklists - **Skill Loading** — References relevant SKILL.md files - **Context Injection** — Pulls memories from Orbit/MCP - **Conventional Commits** — Standardized commit messages - **Pattern Compliance** — Matches existing code style
Full Public Reader
---
name: pulse-v2
description: Governance-aware autonomous development sessions with skill integration, checklist tracking, and conventional commits
homepage: https://github.com/clawdbot/clawdbot
user-invocable: true
command-dispatch: pulsev2
metadata.clawdbot: {"governance": true, "mcp_aware": true}
---
Pulse v2 — Governance-Aware Autonomous Development
Pulse v2 enhances autonomous development sessions with:
- Governance Integration — Reads and updates project checklists
- Skill Loading — References relevant SKILL.md files
- Context Injection — Pulls memories from Orbit/MCP
- Conventional Commits — Standardized commit messages
- Pattern Compliance — Matches existing code style
Quick Start
/pulsev2 @project "goal description"This automatically:
1. Reads `.governance/` files
2. Loads relevant skills
3. Runs the task
4. Updates checklist on completion
5. Commits with conventional format
Task Builder Function
When spawning a Pulse v2 session, the main agent MUST use this structure:
## PULSE v2 PREAMBLE
### Governance
**Project:** {project_name}
**Path:** {project_path}
**Charter:** {path}/.governance/PROJECT_CHARTER.md (read if exists)
**Checklist:** {path}/.governance/CHECKLIST.md (read and update)
**Current Phase:** {N} of {total}
### Skills to Load
Before starting, read these for specialized knowledge:
{list of relevant skill paths}
### Project Context
{Recent work summary or Orbit query results}
### Standards
- [ ] Check existing code patterns before writing
- [ ] Use project's naming conventions
- [ ] Follow folder structure
- [ ] Add inline comments for complex logic
### Commit Format
Use conventional commits:
- `feat(scope): description` — New feature
- `fix(scope): description` — Bug fix
- `docs(scope): description` — Documentation
- `refactor(scope): description` — Code restructure
- `test(scope): description` — Tests
Include phase reference: `feat(phase-3): Add API authentication`
### Completion Checklist
After finishing:
- [ ] Update `.governance/CHECKLIST.md` with status ✅
- [ ] Add session label and commit hash to tracking table
- [ ] Update any relevant documentation
- [ ] Commit all changes
---
## TASK
{actual task description}
---
## DELIVERABLES
1. {deliverable 1}
2. {deliverable 2}
3. Update governance checklist
4. Commit: `{commit format}`Skill Matching Guide
Match task keywords to skills:
| Task Type | Skills to Load |
|---|---|
| iOS/Swift game | `gam:mfp`, `governance-framework` |
| Expo/React Native | `expo-mobile`, `expo-preview` |
| AI features | `nano-banana-pro`, `gemini` |
| Testing | `coding-agent` |
| Video/Media | `vid:remotion`, `video-frames` |
| Creative | `tie`, `art:creative`, `spf` |
Context Injection
From Orbit (if available)
Query: "{project} {feature area} recent work"
Include top 3-5 relevant snippetsFrom Memory
Search: memory/YYYY-MM-DD.md for recent session logs
Extract: relevant decisions, patterns, blockersFrom Governance
Read: .governance/CHECKLIST.md
Extract: current phase, completed items, dependenciesExample: Full Pulse v2 Task
## PULSE v2 PREAMBLE
### Governance
**Project:** Serenity Soother Expo
**Path:** /Users/mo/expo-workspace/serenity-soother-expo
**Charter:** .governance/PROJECT_CHARTER.md
**Checklist:** .governance/PARITY_PIPELINE.md
**Current Phase:** 2 of 12 (Session History)
### Skills to Load
- `[home-path]` — Expo patterns
- `[home-path]` — Checklist management
### Project Context
Phase 1 (Script Library) complete:
- Created app/(auth)/library/ routes
- Added ScriptCard, CategoryFilter components
- Zustand store for scripts
- 10 sample scripts
iOS reference: Features/History/ (1 file)
### Standards
- Use NativeWind/Tailwind for styling
- Follow Expo Router conventions
- Match existing component patterns
- TypeScript strict mode
### Commit Format
`feat(phase-2): Add session history tracking`
### Completion Checklist
- [ ] Update PARITY_PIPELINE.md Phase 2 → ✅
- [ ] Add commit hash to tracking table
---
## TASK
### Goal
Implement session history feature matching iOS functionality.
### Tasks
1. Create `app/(auth)/history/index.tsx` — Session list
2. Create `app/(auth)/history/[id].tsx` — Session detail
3. Create `components/history/SessionCard.tsx`
4. Create `components/history/StatsChart.tsx`
5. Create `lib/history/store.ts` — Zustand state
6. Track: date, duration, script, completion %
7. Add calendar view option
8. Implement streak tracking
### Constraints
- Match iOS feature parity
- Use existing theme/styling
- TypeScript strict
---
## DELIVERABLES
1. Complete history feature
2. Navigation integrated
3. Streak tracking working
4. PARITY_PIPELINE.md updated
5. Commit: `feat(phase-2): Add session history with streaks`Governance File Templates
PROJECT_CHARTER.md
# Project Charter: {Name}
## Overview
{Brief description}
## Scope
- In scope: {features}
- Out of scope: {exclusions}
## Timeline
- Start: {date}
- Target: {date}
## Success Criteria
- [ ] {criterion 1}
- [ ] {criterion 2}CHECKLIST.md
# Implementation Checklist
## Progress Tracking
| Phase | Status | Session | Commit |
|-------|--------|---------|--------|
| 1. {Phase 1} | 🔴 Pending | - | - |
| 2. {Phase 2} | 🔴 Pending | - | - |
## Phase Details
### Phase 1: {Name}
- [ ] Task 1
- [ ] Task 2Benefits Over Pulse v1
| Aspect | v1 | v2 |
|---|---|---|
| Governance | ❌ Ignored | ✅ Read & updated |
| Skills | ❌ Not loaded | ✅ Referenced |
| Memory | ❌ Isolated | ✅ Context injected |
| Commits | Generic | Conventional format |
| Documentation | Optional | Required |
| Tracking | Manual | Auto-updated |
| Code style | Random | Pattern-matched |
Troubleshooting
Sub-agent didn't update checklist?
- Ensure checklist path is correct in preamble
- Verify file is writable
- Check if task explicitly requires update
Skills not being used?
- Verify skill paths exist
- Include explicit "Read this skill" instruction
- Check skill descriptions match task
Context missing?
- Orbit may not be connected
- Memory files may not exist
- Add context manually to preamble
Promotion Decision
Attach run IDs, datasets, metrics, and reproduction commands.
Source Anchor
homelab/clawdbot/skills/pulse-v2/SKILL.md
Detected Structure
Method · Evaluation · References · Code Anchors · Architecture