applying-effort-policy

Resolve effective Claude model and effort per role tier for session spawning.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/tuvens/phased-development --skill applying-effort-policy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: applying-effort-policy
Source: https://github.com/tuvens/phased-development/tree/main/skills/applying-effort-policy
Command: npx skills add https://github.com/tuvens/phased-development --skill applying-effort-policy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes ambiguity from session spawning by determining the exact Claude model and effort level to use for each role tier, so orchestrators and templates stay consistent without manual guesswork.

Core Features & Use Cases

  • Policy Resolution: Reads the effective effort policy overlay and applies the correct precedence across spawn-time overrides, role overrides, task-type overrides, and baseline doctrine.
  • Session Spawning Support: Supplies concrete model and effort values when rendering role templates or launching child sessions such as phase, epic, sprint, and task agents.
  • Validation and Fallbacks: Validates the policy JSON, tolerates missing or invalid overlays, and falls back to the doctrine baseline when needed.
  • Use Case: A lead session can spawn a sprint agent with the correct tier settings while preserving consistent defaults across the whole project.

Quick Start

Ask the skill to resolve the effective model and effort for a target tier and role, then use the returned values when spawning the next Claude session.

Frequently Asked Questions about applying-effort-policy

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

FAQPage Schema
How do I resolve the correct Claude model and effort level for spawned sessions?

Resolving the correct Claude model and effort level for spawned sessions involves applying a policy overlay that checks spawn-time overrides, role templates, and task-type precedence to return concrete configuration values. This ensures orchestrators launch child sessions with the exact tier settings required.

What happens when the effort policy JSON overlay is missing or invalid during session spawning?

When the effort policy JSON overlay is missing or invalid during session spawning, the resolution process validates the JSON structure and automatically falls back to the doctrine baseline configuration. This guarantees spawned sessions still receive valid model and effort settings without manual intervention.

How do role templates and task-type overrides interact when determining Claude tier configuration?

Role templates and task-type overrides interact through a strict precedence hierarchy where spawn-time overrides take priority, followed by role-specific overrides, task-type overrides, and finally the baseline doctrine. The resolution applies this cascade to yield the effective model and effort values for each session.

Can I apply effort policy resolution across both canonical plugin and consumer mirror policy files?

Effort policy resolution works across both plugin canonical and consumer mirror policy files by reading the JSON overlay from either source. It validates the structure and applies the appropriate precedence rules so spawned sessions use consistent configurations regardless of the file origin.

What is the best way to ensure consistent Claude model settings across orchestrator child-spawn commands?

Ensuring consistent Claude model settings across orchestrator child-spawn commands requires resolving the effective effort policy before rendering templates or launching agents. The resolution validates overlays, honors precedence, and supplies concrete values so phase, epic, sprint, and task agents all inherit correct tier configurations.

Do I need a valid JSON overlay to spawn sprint or task agents with specific effort levels?

A valid JSON overlay is not strictly required to spawn sprint or task agents because the resolution tolerates missing or invalid files by falling back to the doctrine baseline. However, providing a valid overlay lets you define custom role and task-type overrides for precise effort control.