Feature Request: Per-task effort level configuration

Feature Request

Problem

The effort level setting (low/medium/high/max) is currently global for the entire session. When working on diverse tasks with varying complexity, I have to manually toggle effort via /model between tasks. For example:

• High effort needed for: writing design proposals, architecture planning, complex code generation
• Low effort sufficient for: time logging, simple issue creation, status updates

Manually switching effort levels between tasks is friction that adds up over a session.

Proposed Solution

Allow per-skill or per-command effort level configuration. Some possible approaches:

1. Skill frontmatter — let skills declare their preferred effort level:

``yaml
# skill: openspec-new
# effort: high
``

1. Settings-based mapping — configure effort per skill in settings:

``json
{
"effortBySkill": {
"openspec-new": "high",
"openspec2gh": "high",
"time-log": "low",
"issue-create": "low"
}
}
``

1. Inline override — specify effort when invoking a command:

``
/openspec-new --effort high
``

Use Case

I use Claude Code with custom skills for project management (issue tracking, time logging, OpenSpec proposals). Simple skills like /time-log don't need deep reasoning, but /openspec-new benefits greatly from high effort. Being able to configure this once and forget about it would improve the workflow significantly.

Current Workaround

Manually toggle effort via /model before running different types of tasks.