Use when asked to triage, rank, prioritise or organise the open issues of a repo or of a whole org; when asked for a backlog board or "what should we work on next"; or when asked to refresh or sync an existing triage.
Use when asked to triage, rank, prioritise or organise the open issues of a repo or of a whole org; when asked for a backlog board or "what should we work on next"; or when asked to refresh or sync an existing triage.
Use when asked what a run or session cost, where the money went, whether a process change made the pipeline cheaper, or to compare runs before and after a change; when asked for an audit page or an architecture page of the fr pipeline; or when a PR body needs its usage table.
Review ONE freshly written design spec, read-only, in a context separate from the one that wrote it, and return a structured list of findings. fr-goal dispatches it at spec-review, into the fr-isolation workspace the spec lives in — never into a second worktree, which would be cut from main where the feature branch's…
Review ONE freshly written design spec, read-only, in a context separate from the one that wrote it, and return a structured list of findings. fr-goal dispatches it at spec-review, into the fr-isolation workspace the spec lives in — never into a second worktree, which would be cut from main where the feature branch's…
Review ONE freshly written design spec, read-only, in a context separate from the one that wrote it, and return a structured list of findings. fr-goal dispatches it at spec-review, into the fr-isolation workspace the spec lives in — never into a second worktree, which would be cut from main where the feature branch's…
Review ONE freshly written design spec, read-only, in a context separate from the one that wrote it, and return a structured list of findings. fr-goal dispatches it at spec-review, into the fr-isolation workspace the spec lives in — never into a second worktree, which would be cut from main where the feature branch's…
Use when asked what a run or session cost, where the money went, whether a process change made the pipeline cheaper, or to compare runs before and after a change; when asked for an audit page or an architecture page of the fr pipeline; or when a PR body needs its usage table.
Use when asked where a repo's recent bugs came from, to classify the issues filed in a window by origin (latent, regression, new feature, leftover, gap, duplicate), to build a defect-origins page, or to explain which process change would have prevented them.
Use when asked where a repo's recent bugs came from, to classify the issues filed in a window by origin (latent, regression, new feature, leftover, gap, duplicate), to build a defect-origins page, or to explain which process change would have prevented them.
★not rated 2▲
+1 2d agoA56 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: