executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
grpc-and-language-sdksOperate Bindu's gRPC core, proto contract, and TypeScript SDK lifecycle for language-agnostic agents.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this sub-skill for Bindu agents written outside Python: core gRPC service, SDK callback servers, GrpcAgentClient, shared proto fields, TypeScript @bindu/sdk, heartbeat/registration lifecycle, proto regeneration, and gRPC troubleshooting.
../agent-authoring-and-a2a/.../security-identity-and-payments/.../deployment-runtime-and-operations/.references/grpc-architecture.md — two services, directions, ports, registration, registry, heartbeat, and runtime message flow.references/typescript-sdk.md — TS config/types, skill loading, callback server, response mapping, cleanup.references/proto-and-regeneration.md — proto messages, generated-code policy, regeneration commands.references/troubleshooting.md — connection, registration, timeout, callback, heartbeat, proto, streaming, and skill-content issues.scripts/check_proto_regen_readiness.py — read-only regeneration readiness check.localhost:3774; HTTP/A2A defaults to localhost:3773.AgentHandler callback gRPC server on an explicit or auto-assigned port.BinduService.RegisterAgent accepts config_json, skills, and grpc_callback_address, creates GrpcAgentClient, and runs shared Bindu core setup in the background.AgentHandler.HandleMessages returns plain content for completion or non-empty state/prompt for open task states.proto/agent_handler.proto, then regenerate.