technical-feasibility-study SKILL.md skillA
technical-feasibility-study from fattain-naime/engineering-docs is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add fattain-naime/engineering-docs/technical-feasibility-study@git:20260717.2f82174Pins git:20260717.2f82174 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- fattain-naime/engineering-docs
- Path
skills/technical-feasibility-study/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260717.2f82174, committed Jul 17, 2026
- First version recorded
- Jul 8, 2026
- Size
- 12,667 bytes
- Repository stars
- 6
- License
- MIT
Assess whether a proposed technical solution is viable given the current stack, team, timeline, and constraints. Produces a go/no-go recommendation with evidence. Use before committing engineering resources to design or implementation.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
## Purpose Prevent the most expensive engineering failure mode: committing significant resources to a direction that was never viable. A technical feasibility study is not a design document - it does not specify how to build something. It answers the prior question: **should we build it this way at all?** ## Input **Works best with:** A description of the proposed concept, approach, or technology being evaluated. **Also valuable:** Timeline constraints, team skills inventory, existing tech stack, budget limits, regulatory environment. **Example invocation:** `Assess the feasibility of building a real-time fraud detection engine using stream processing for our payment gateway, given our team of 3 PHP engineers and a 4-month delivery window.` ## Key Concepts ### Four Feasibility Dimensions **1. Technical Feasibility** Can this be built with available or acquirable technology? Does the proposed solution have proven precedent at similar scale? Are there known technical blockers? **2. Resource Feasibility** Do we have - or can we acquire - the engineering skills, infrastructure, and budget required? What is the realistic timeline given current team capacity? …
Read the whole file at its exact version.
How to install
mdr add fattain-naime/engineering-docs/technical-feasibility-study@sha256:ac955bbb3828e2c6The line at the top of this page pins the label git:20260717.2f82174, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_innoxkrsr4xsso6u)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Jul 8, 2026 and Jul 17, 2026, about one every 2 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260717.2f82174 latest | 2026-07-17 | 2f82174 | 12,667 B | A | view · diff |
| git:20260712.59c5852 | 2026-07-12 | 59c5852 | 5,186 B | A | view · diff |
| git:20260712.7e3d1bb | 2026-07-12 | 7e3d1bb | 5,270 B | A | view · diff |
| git:20260709.03fe43c | 2026-07-09 | 03fe43c | 5,068 B | A | view · diff |
| git:20260708.a309efd | 2026-07-08 | a309efd | 4,229 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (12667 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
fattain-naime/engineering-docs · 6 stars · license MIT · pushed 2026-10-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_innoxkrsr4xsso6u GET https://markdownregistry.com/api/v1/resolve?ref=fattain-naime/engineering-docs/technical-feasibility-study GET https://markdownregistry.com/api/v1/blob/ac955bbb3828e2c6d5ef3b188fb8d215cd11794e9963b3042000dfdeb520e09a
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.