globus-mcp: Skill for Claude Code

globus-feature — shape the goal

When to Use

Invoke /globus-feature on a clean main to begin a new unit of work. It produces exactly one artifact — a refined spec/{slug}/GOAL.md on a fresh branch — and stops for your sign-off before the expensive /globus-plan step. This is shaping, in the Shape Up sense: make the goal coherent, bounded, and unambiguous, but leave design freedom for the plan. Do not research or read a lot of code here.

Reference (load only if needed): .agents/factory/methodology.md, .agents/factory/ears.md, the template .agents/factory/templates/GOAL.md.

Harness portability. These skills run on any harness, not only Claude Code — see factory/portability.md. Here the Claude-specific affordances degrade gracefully: if the Current state block below isn't auto-injected, run those commands yourself in Step 1; if AskUserQuestion is unavailable, ask in plain text and STOP. Everything else (git) is portable shell.

User Instructions

Additional instructions provided with the invocation: $ARGUMENTS

Current state (injected at load)

• Branch: !git branch --show-current
• Tree: !git status --porcelain | head -n 20
• Untracked GOAL.md files: !git ls-files --others --exclude-standard 'spec/**/GOAL.md'
• Open issues: !git ls-files 'issues/*.md'

Argument Parsing

Parse $ARGUMENTS case-insensitively. If self-contradictory, STOP and ask.

• A path matching spec/<slug>/GOAL.md → adopt that file as the seed; {slug} is taken from the path. (This is the "I hand-wrote a GOAL.md" flow.)
• A path matching issues/<slug>.md (or .security/issues/<slug>.md) → promote that issue. {slug} is the file stem; its frontmatter supplies kind and appetite unless the invocation overrides them. A bare {slug} naming an existing issues/{slug}.md resolves the same way. See "Promoting an issue" in Step 4.
• fix / bug / refactor → set kind; otherwise infer from the wording, defaulting to feature.
• appetite small / appetite big → set appetite; else default small for kind: fix, big for feature/refactor. Those two values are the whole vocabulary; a seed whose frontmatter still reads medium rounds up to big, because rounding up costs a research fan-out while rounding down fails globus-review's scope check against a contract a human already accepted. Record the round-up as a dated Clarification in the GOAL; leave the seed's own frontmatter alone.
• Everything else → the inline feature description (the seed prompt).
• No arguments and no untracked spec/*/GOAL.md present → STOP and ask for a description or a GOAL.md path.