using-pulse

Route Pulse sessions to the correct next skill after preflight or resume.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/quanpersie2001/pulse --skill using-pulse
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: using-pulse
Source: https://github.com/quanpersie2001/pulse/tree/main/plugins/pulse/skills/using-pulse
Command: npx skills add https://github.com/quanpersie2001/pulse --skill using-pulse

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires node-runtime, beads-cli, beads-viewer, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This meta-skill routes Pulse sessions after preflight and on resume, ensuring correct gating and memory alignment so work does not proceed with uncertain state.

Core Features & Use Cases

  • Route to the next Pulse skill (exploring, planning, validating, swarming, executing, reviewing, or compounding) based on current state.
  • Verify onboarding health, tooling readiness, and memory state before moving forward.
  • Manage resume and pause contracts through owner-scoped handoffs to keep work auditable.

Quick Start

Route the current Pulse session to the correct next skill after preflight or resume, based on the current state.

Frequently Asked Questions about using-pulse

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

FAQPage Schema
How do I route a Pulse session to the correct next skill after preflight?

To route a Pulse session after preflight, the system verifies onboarding health, tooling readiness, and memory pointers before handing off to the next skill based on the current state.

What is the best way to resume paused work in a Pulse gate sequence?

Resuming paused work in a Pulse gate sequence involves verifying memory alignment and routing the session through owner-scoped handoffs to keep work auditable and prevent uncertain state.

How does mode-aware routing across the Pulse gate sequence work?

Mode-aware routing across the Pulse gate sequence works by evaluating the current state to direct the session to exploring, planning, validating, swarming, executing, reviewing, or compounding skills.

Do I need to verify onboarding health before moving forward with a Pulse session?

Yes, you need to verify onboarding health, tooling readiness, and memory state before moving forward to ensure work does not proceed with uncertain state during bootstrapping or resuming.

Why does a Pulse session require preflight checks before executing the next skill?

A Pulse session requires preflight checks to ensure correct gating and memory alignment, preventing work from proceeding with uncertain state and verifying tooling readiness before handoff.

Can I use node-runtime and beads-cli to manage Pulse session routing contracts?

Yes, you can use node-runtime and beads-cli dependencies to manage Pulse session routing contracts, ensuring owner-scoped handoffs and memory alignment are maintained during pause and resume operations.