nolte-goose
Goose recipe lifecycle: requirements, plan, implementation and audit against a pinned, source-backed baseline. Requires Goose 1.45.0 and the nolte-shared plugin.
Plugin nolte-goose from marketplace nolte-goose in nolte/claude-goose. Commands read from the repo's manifest — 7 days ago.
What it installs
Skills (14)
speckit-analyzePerform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
speckit-checklistGenerate a custom checklist for the current feature based on user requirements.
speckit-clarifyIdentify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
speckit-constitutionCreate or update the project constitution from interactive or provided principle inputs, ensuring all dependent templates stay in sync.
speckit-convergeAssess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
speckit-implementExecute the implementation plan by processing and executing all tasks defined in tasks.md
speckit-planExecute the implementation planning workflow using the plan template to generate design artifacts.
speckit-specifyCreate or update the feature specification from a natural language feature description.
speckit-tasksGenerate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.
speckit-taskstoissuesConvert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.
recipe-auditAudits a Goose recipe or extension configuration against a pinned baseline revision by invoking the review process's Claude Code binding with the process's own five inputs; states no rule of its own and evaluates no criterion. The rules live in the process's `constraints.md`; the criteria in the pin
recipe-implementWrites a Goose recipe and its declared extension configuration from a ready recipe plan, one element per plan entry, each traced back by comment, and validates it with Goose's own parser before reporting done. Does not open a pull request; use `nolte-shared:pull-request-create` for that. Invoke when
recipe-planPlans a Goose recipe from a confirmed recipe requirement artifact: maps every requirement to a recipe element, marks every applicable baseline criterion satisfied by construction or a risk, and returns requirements that cannot be built as named conflicts. Use `nolte-engineering:implementation-plan-a
recipe-requirements-elicitCaptures what a Goose recipe must do, as an artifact a stranger can build from. Delegates the interview method and the generic requirement artifact to `nolte-shared:requirements-elicit`; adds only the questions a Goose recipe needs answered — inputs, host capabilities, execution mode, output shape,
Maintain nolte-goose?
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.