Skip to content
Skills Library
Management & product · Analysis

gate

/gate

Feasibility gate. Decides GO, GO_WITH_NOTES or STOP for an initiative or a single story before planning or coding, from evidence in the repository and current docs. Use when the user, lead or story asks whether work is ready to start.

Author
bitIO ↗
Repository
wheelhouse ↗
Licence
MIT
Last repository change
12.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 12.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Feasibility gate. Decides GO, GO_WITH_NOTES or STOP for an initiative or a single story before planning or coding, from evidence in the repository and current docs. Use when the user, lead or story asks whether work is ready to start.

Original author description

Feasibility gate. Decides GO, GO_WITH_NOTES or STOP for an initiative or a single story before planning or coding, from evidence in the repository and current docs. Use when the user, lead or story asks whether work is ready to start.

How it works

  1. Modes
  2. Investigation order
  3. Risk level
  4. Outcomes
  5. Output
Original SKILL.md headings · 70 lines, 429 words
SKILL.md preview
---
name: gate
description: Feasibility gate. Decides GO, GO_WITH_NOTES or STOP for an initiative or a single story before planning or coding, from evidence in the repository and current docs. Use when the user, lead or story asks whether work is ready to start.
---

# Gate

Answer one question: **should we start building this now?** Not "can I imagine a better architecture?"

Protect the team from expensive mistakes without becoming a bottleneck. **Block risks, not preferences.**

## Modes

- **initiative** (from `lead`): a full assessment, before the backlog is written.
- **story** (from `story`): five lines at most, focused on what this story touches.

## Investigation order

1. **Outcome.** Restate what is being built in one or two lines. If you can't, it's a product gap.
2. **Repository.** How does the code do this today? Boundaries, existing patterns, tests, contracts, deploy configuration. Evidence wins over the issue's wording: a detailed spec can still describe an architecture the repo contradicts.
3. **Impact.** Which packages, contracts, data and deployments change?
4. **External assumptions.** Check library and framework claims against current official docs. Never trust memory for versions or APIs.

## Risk level

| Level | Examples | Depth |
|---|---|---|
| Low | isolated UI, copy, small internal refactor | quick look |
| Medium | new API, database change, cross-package change | normal |
| High | auth, authorization, payments, destructive migration, public contract, infrastructure, runtime or framework swap | deep, and load the matching `check-*` skills |

High-risk areas to probe:

- **Data**: destructive migrations, backfills, uniqueness, referential integrity, rollback, existing rows (`check-data`).
- **Security**: authentication, authorization, secrets, tokens, trust boundaries (`check-security`).
- **APIs**: public contracts, backwards compatibility, serialization, error formats.
- **Infrastructure**: deploy constraints, environment variables, ports, runtime compatibility.
- **Performance**: only if the change could materially affect it (`check-perf`).
- **Testing**: can the acceptance criteria actually be verified? (`check-testing`)

## Outcomes

- **GO**: understood, no material blockers.
- **GO_WITH_NOTES**: implementable. The notes are constraints that planning must carry.
- **STOP**: something material must be resolved first. Say which kind:
  - **product gap**: contradictory requirements, or a missing decision that changes behaviour
  - **technical**: impossible requirement, incompatible architecture, unsafe migration, security flaw, false library assumption, violation of a hard repo constraint

STOP should be rare. Never STOP because you'd prefer another framework, structure, name or abstraction.

## Output

Initiative mode:

```markdown
## Gate: GO | GO_WITH_NOTES | STOP

**Understood:** <one or two lines>
**Evidence:** <facts with file:line or URL>
**Material risks:** <only what matters to delivery, or "none identified">
**Assumptions:** <what the plan relies on>
**Notes / blockers:** <constraints to carry, or exactly what must be resolved and by whom>
```

Story mode:

```markdown
Gate: GO_WITH_NOTES · Risk: high · Checks: security
- <note 1>
- <note 2>
```

You don't write code and you don't edit issues. The caller does that.

Versions

RepositoryScoreLicence
This page · bitIO/wheelhouse100MIT
sh5623/e2e-rail100MIT
skillberry-ai/cap-evolve100Apache-2.0
Perchusha/pitwall100MIT
jease0502/research-agent-kit100Apache-2.0
jeffersonvalente/cardume100MIT
Vibecheck-QA/vibecheck100MIT
iankiku/forwward-teams100MIT
fdu-ins/insurance-skills100Apache-2.0

Database snapshot: 13.11.2026 · package version 83ead95b91ee (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100spec
    Write the spec for a Ready story as its own PR and stop at Spec review. Use when asked to spec a story, write the spec for an issue, or start the next Ready story. Implementing an Approved story is /next.
  • 100story-readiness
    Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story…
  • 100story-readiness
    Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story…
  • 100story-readiness
    Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story…
  • 100014-agile-user-story
    Guides the creation of agile user stories. Use when the user wants to create a user story. This should trigger for requests such as Create a user story; Write a user story; I need to write a user story; Split feature requirements into user stories. Part of Plinth Toolkit
  • 100discovery
    Phase 0 validation gate — problem framing, competitive analysis, feasibility, and a go/no-go checkpoint before committing to a feature. Use when evaluating whether an idea is worth building, before /story or /design. Trigger on "is this worth building", "validate this idea",…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.