stride-creating-goals

Validate batch goal payloads with a "goals" root key and nested task specifications.

5|3|Updated Oct 19, 2025
One-click install
npx skills add https://github.com/cheezy/kanban --skill stride-creating-goals
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stride-creating-goals
Source: https://github.com/cheezy/kanban/tree/main/docs/multi-agent-instructions/skills/stride-creating-goals
Command: npx skills add https://github.com/cheezy/kanban --skill stride-creating-goals

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

INTERNAL — invoked only by stride:stride-workflow. Do NOT invoke from a user prompt. Contains the goal/batch creation contract (POST /api/tasks/batch root key MUST be "goals" not "tasks", dependency index format), used during the orchestrator's goal-decomposition phase.

Core Features & Use Cases

  • Validates batch payload for the root key "goals" and ensures proper task nesting.
  • Enforces dependency formatting (within-goal indices) and prevents cross-goal references in batch operations.
  • Guides safe, deterministic goal orchestration in AI-assisted Kanban workflows.

Quick Start

Frame all batch goal creations with the root key 'goals' and ensure proper nested task specifications.

Frequently Asked Questions about stride-creating-goals

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

FAQPage Schema
How do I structure a batch goal creation payload for an API orchestrator?

Batch goal creation payloads require a root key named "goals" containing nested task specifications. This ensures the orchestrator correctly processes multi-goal batches during the automated goal-decomposition phase without structural errors.

What is the correct dependency index format for multi-goal batch operations?

Dependency formatting in batch operations uses within-goal indices to reference tasks. Cross-goal references are explicitly prevented to maintain deterministic goal orchestration and ensure safe execution within AI-assisted Kanban workflows.

Can I use batch goal creation for AI-assisted Kanban workflow automation?

Batch goal creation is designed for AI-assisted Kanban workflows and is safe to run in automated environments. It enforces deterministic goal orchestration by validating payload structure and dependency conventions during the decomposition phase.

Why does my batch API call fail when using the root key "tasks" instead of "goals"?

Batch API creation calls fail because the root key must be "goals", not "tasks". This enforces proper task nesting and validates the batch payload structure before processing multi-goal operations in the orchestrator.

What are the limitations of cross-goal dependency references in batch payload validation?

Cross-goal dependency references are blocked during batch payload validation to prevent unsafe orchestration. Dependencies must use within-goal indices, ensuring deterministic execution and structural integrity across multi-goal batches.