Skip to content

rhei-template-writer never states where an instantiated workspace lands #112

Description

@vjovanov

Problem

crates/rhei-cli/skills/rhei-template-writer/SKILL.md:242 documents --output as a constraint only:

| --output <path> | Must not already exist (except under --dry-run); instantiation refuses to merge/overwrite. |

It never says where an instantiated workspace lands when --output is omitted, so an agent reading the skill cannot tell the user where the workspace will appear, or reason about the refusal above — which is about a path the skill never names.

The default is specified: docs/functional-spec/rhei-templates.spec.md:470-476 — "Run inside a project, a template's default output is <project>/<template-name>/", falling back to ./<template-name>/ outside one. The CLI's own help carries it too (rhei-templates.spec.md:297-298).

This is the same class of gap as #68: the skill specifies format thoroughly and filesystem outcome barely. ## File Placement (SKILL.md:222) covers where templates live, which is a different question and is correct.

Expected

Name the default in the --output row, so the constraint and the path it applies to are stated together:

| --output <path> | Defaults to <project>/<template-name>/ inside a Panta project, else ./<template-name>/. Must not already exist (except under --dry-run); instantiation refuses to merge/overwrite. |

Found while fixing #68.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions