Feasibility Check
Use before committing to a project or initiative — to decide whether the goal is achievable within the real constraints, and surface the risks that could sink it. Points the riskiest unknowns at a prototype.
Install
$ agentstack add skill-njoyimpeguy-augments-feasibility-check ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-njoyimpeguy-augments-feasibility-check) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Feasibility Check
Optimism is not a plan. Before a project is greenlit, find the thing most likely to kill it — and decide honestly whether it's achievable.
When to use
- Before committing to a project or initiative (the go/no-go moment).
- When feasibility is genuinely uncertain — new tech, hard constraints, unknown data.
- Skip when the path is well-trodden and the risk is obviously low.
Procedure
- List the hard constraints: time, team, budget, tech, data, external dependencies, compliance.
- Find the killer risks: the assumptions that, if false, sink the project. Rank them by likelihood × how fatal.
- Reduce the top unknowns cheaply — usually a small spike (see
prototyping), not more discussion. - Give a verdict: go / no-go / go-if (with the conditions that must hold). A no-go now is far cheaper than a failure later.
- Write the
## Feasibilitysection of the project brief: constraints, top risks, the verdict and its conditions.
A go hands off to scope-it — draw the boundary before design.
Common mistakes
- Greenlighting on optimism — no named risks means you didn't look.
- Treating "we'll figure it out" as feasibility — name what would make it infeasible.
- Endless analysis instead of a cheap spike to kill the biggest unknown.
- Skipping Option Zero — the cheapest path is sometimes to not build it: an existing tool, a config change, or a smaller change to the problem. Rule it out before greenlighting a build.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: NjoyimPeguy
- Source: NjoyimPeguy/augments
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.