agentleFS
max-roguemax-rogue/Stackmoss/.agents/skills/intake-engine/SKILL.md

intake-engine

Skill4 starsChanged 8 months agoMITView on GitHub

StackMoss CLI intake flow — Fast mode (6 questions), Interview mode (12 questions), persona detection, decision tree, pack overlay composition, and completeness gates. Use when working on the onboarding questionnaire or pack selection logic.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Completeness gate: Only check Q5. If missing → re-ask Q5 once.

    line 26
  2. Distinctive:

    Never infer, never assume, never use default for critical fields

    line 69
  3. Distinctive:

    Use LLM for pack/role selection logic

    line 78
  4. Distinctive:

    Add questions not in the BRD schema

    line 80

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Intake Engine Skill

When to Use

  • Implementing the intake questionnaire (Fast/Interview mode)
  • Building the persona detection + pack selection logic
  • Working on completeness gates
  • Implementing the 2D Matrix overlay compose (UserType × ProjectType)

Intake Modes

Fast Mode (6 questions, ~3 min)

#QuestionChoices
Q1Role in project?Biz lead / Dev lead / Solo / Unknown
Q2Who is the product for?Individual / SME / Enterprise / Community
Q3Geography?Internal / VN / Global
Q4Primary channel?Web / Mobile / Chat / API
Q5Sensitive data?None / PII / Finance / Compliance
Q6First feature to ship?(free text + appetite S/M/L)

Completeness gate: Only check Q5. If missing → re-ask Q5 once. Do NOT check outcome/non-goals (avoid turning Fast into Interview).

Interview Mode (12 questions, ~10 min)

  • Block 1 (Q1–Q4): Business context
  • Block 2 (Q5–Q8): Technical constraints
  • Block 3 (Q9–Q12): Team & velocity

Completeness gate: Full check — must have "for who", measurable outcome, at least 1 non-goal. If missing → up to 2 targeted follow-up questions.

2D Matrix: Pack Selection

UserType overlay × ProjectType overlay → Role set
UserTypeProjectTypeRoles
BizLedMVPTL, BA, DEV, QA(light), DOCS
BizLedProductionTL, BA, DEV, QA(strong), OPS(light), DOCS
DevLedMVPTL, DEV, QA, DOCS (BA-lite in TL)
DevLedProductionTL, DEV, QA(strong), OPS, DOCS
SoloMVPTL, DEV, QA(light)
SoloProductionTL, DEV, QA, DOCS
NewbieanyTL(guide), DEV(small), QA(checklist), DOCS

Auto-add Rules (no user prompt needed)

  • Q5/Q6 = PII / Finance / Compliance → add SEC-lite
  • Q7 = VPS / Cloud AND Q2 = SME / Enterprise → add OPS-lite

Architecture Rules

Decision Tree (deterministic, no LLM)

src/intake/
├── questions.ts       → Question definitions + validation
├── fast-mode.ts       → 6-question flow + completeness gate
├── interview-mode.ts  → 12-question flow + completeness gate
├── pack-selector.ts   → 2D matrix overlay compose
└── auto-add.ts        → SEC-lite / OPS-lite auto-detection

Skipped Questions

  • Any skipped question → write to OPEN_QUESTIONS.md
  • Never infer, never assume, never use default for critical fields

Authority Sources

  • BRD §5: Personas (P1–P4)
  • BRD §8: Phase A intake flow (Fast + Interview)
  • BRD §10: Framework Packs (overlay compose + role mapping)
  • BRD §11: BYO-LLM (optional enhancement)

Do NOT

  • Use LLM for pack/role selection logic
  • Infer answers to skipped questions
  • Add questions not in the BRD schema
  • Turn Fast mode into Interview mode via extra validation

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.