mcpField
G
goal

goal

github.com/gabriel-lafranceAgent workflows062 installsUpdated 1d ago
Repository

About goal

goal is an orchestration skill for coding agents that guides work from grilling and planning through implementation, acceptance evidence, and code review. It uses shared project doctrines and task workers, with explicit rules for nested work and shipping authority.

Key features

  1. 01Orchestrates grill, plan, and implementation
  2. 02Requires shared taste and architecture doctrines
  3. 03Dispatches task workers in waves
  4. 04Collects acceptance evidence and code review
  5. 05Defines shipping and nested-work boundaries

Use cases

  1. 01Coordinating a repository change from discussion to review
  2. 02Splitting implementation into task-worker waves
  3. 03Returning completion evidence to a parent workflow

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/gabriel-lafrance/skills --skill goal

After installing, type/goalin Claude Code to confirm it loaded.

Bundled filesdoctrine.mdreference.md

Details

From the project README

Goal

Must read: ../pack-shared/standards.md — Read /taste and /architecture doctrines this turn before grilling, planning, or implementing. Do not skip.

Execution context: ../pack-shared/execution-context.md · Read: doctrine.md · reference.md · Ask style: ../pack-shared/asking.md · Browser: ../pack-shared/browser-evidence.md · PR ship: ../pack-shared/pr-ship.md when this chat opens a PR

Orchestrator only. Dispatch Task workers per ../pack-shared/subagents.md. Always load /taste and /architecture during grill and before every implement wave.

/goal follows the stateless execution-context contract: plans are inline unless the user explicitly requests a saved artifact and approves its destination.

Process

  1. Establish or refresh the in-chat execution context. If a parent already supplied ticket, lane, Done when, non-goals, Active Rules, fixed point, and slice bounds, accept that brief. Do not re-derive ticket or branch ownership the parent holds.
  2. Run the lifecycle: grill (unless skip-grill applies) → plan → implement → acceptance evidence → /code-review → Fix mode as needed. Task waves follow subagents.md. Always load /taste and /architecture during grill and before every implement wave.
  3. Announce completion.
If a parent already owns the ticket, branch, and PR

Do not ask ship Questions. Do not commit, push, or open a PR from this skill. Return a completion summary plus evidence envelope to the parent.

If this chat owns shipping

Offer ship Questions only after all gates pass (see reference.md). Do not commit or open a PR unless the user answers yes. If they ask to open a PR, follow ../pack-shared/pr-ship.md. Do not invent a parent.

Recovery, progress, lookup, and safety rules live in the doctrine and reference.

Anti-patterns

  • Asking ship Questions when a parent owns shipping
  • Pushing, committing for ship, or opening a PR when nested

Comments

Markdown supported