requirements-intake skillA
requirements-intake is agent-read markdown (skill) from vmobifystudio/app-dev-team: Use at the very start of a new app project to convert a one-line idea or rough brief into a structured requirements document the CEO/CPO/CTO agents can act on. Triggers when the user says "build an app", "I have an idea for an app", or kicks off /app-init with a fuzzy prompt..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Requirements intake
You are converting fuzzy human intent into a structured intake doc. You are not the CEO yet — you are the funnel.
## When to use
- User starts a project with a one-liner ("Build a habit tracker", "An app for X")
- The CEO agent needs a clean input
- `/app-init` is called
## Procedure
1. Read what the user said. Extract whatever's already there:
- Product idea
- Target user (if named)
- Platform preference (if named)
- Constraints (timeline, budget, must-haves)
2. For everything missing, ask the user **in one round** with at most 5 questions. Use the AskUserQuestion tool if available. Cluster questions; don't drip them.
The five questions, in priority order:
1. Who is this for? (one specific persona, not a market)
2. What is the single most important thing they'll do in the app?
3. What kind of product is this — **iOS app, Android app, both, web app, backend service, CLI
tool, or a library**? If more than one, which ships first?
This question used to ask "iOS, Android, or both", which could not describe a product that is
neither. `role-activation` reads its answer to decide which specialists exist at all, and a
…Read the whole file at its exact version.
How to install
mdr add vmobifystudio/app-dev-team/requirements-intake@git:20260729.c01da4amdr add vmobifystudio/app-dev-team/requirements-intake@sha256:79772f8f0d893cb1Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_tl6h6vilgzh243fi)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260729.c01da4a latest | 2026-07-29 | c01da4a | 3,125 B | A | view · diff |
| git:20260729.d5165d9 | 2026-07-29 | d5165d9 | 2,373 B | A | view · diff |
| git:20260601.0c38fba | 2026-06-01 | 0c38fba | 1,928 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 (3125 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
vmobifystudio/app-dev-team · 4 stars · license MIT · pushed 2026-09-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_tl6h6vilgzh243fi GET https://markdownregistry.com/api/v1/resolve?ref=vmobifystudio/app-dev-team/requirements-intake GET https://markdownregistry.com/api/v1/blob/79772f8f0d893cb1a464fa865189e034dd44f168af2002a1fd9e2932153fee96
Your agent 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.