Plugins sub-flow uses 'location' instead of target_scope (asymmetric vs other sub-flows) #156

Context

After the recent target_scope refactor (PR #155), 6 of the 7 sub-flows in 03-context-generate use the target_scope / target_base pattern: project_root (CWD-relative) or plugin:<name> (plugins/<name>/).

The plugins sub-flow (actions/plugins/01-capture-plugin-intent.md, 02-scaffold-tree.md, 03-seed-first-skill.md) uses a DIFFERENT pattern: location: local|global + plugin_root. This is asymmetric.

Why intentional (probably)

A plugin scaffold IS the target dir. The plugin being created IS the new dir. So target_scope doesn't apply.

What to consider

• Document the asymmetry explicitly in the SKILL.md sub-flows table or in references/
• Or, unify the model: 'target_scope' for projects, 'plugin_root' for plugin authoring; make clear they're different concerns.

Source

Surfaced by E2E test pass on PR #155.

🤖 Generated with Claude Code