How do I install the Kiss Arch Intake skill?

Run npx skillmds@latest add dauquangthanh/kiss-arch-intake in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Kiss Arch Intake safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Kiss Arch Intake?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Kiss Arch Intake free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Kiss Arch Intake?

dauquangthanh (@dauquangthanh) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Kiss Arch Intake by dauquangthanh — Agent Skill

Name: Kiss Arch Intake
Author: dauquangthanh

Kiss Arch Intake

Captures architecture inputs — quality attributes ranking, hard constraints, team context, operational envelope, integration surface, deployment preferences — into a single intake artefact the architect works from. Use when starting system design, capturing requirements for an architecture, or before producing ADRs and C4 diagrams.

dauquangthanh Updated Sep 17, 2026

File contents

User Input

$ARGUMENTS

Audience and tone (interactive mode)

When KISS_AGENT_MODE=interactive (the default), assume the user has limited technical background and limited domain knowledge — they may know basics but lack deep expertise in this skill's area. Run this skill as a guided questionnaire:

One question at a time. No walls of questions.
Yes / no first. Phrase so yes, no, not sure, or skip is a valid answer.
Translate jargon, don't strip it. Use the technical term but always pair it with a plain-English gloss the first time it appears.
Choices, not blank fields. When yes/no isn't enough, offer 2-4 lettered options (A/B/C/D) with one-line plain-language descriptions of the trade-off. Always include "Not sure — pick a sensible default".
Always recommend. State the option you would pick and why in one sentence so the user can reply "yes" / "ok" to accept. Pull defaults from upstream artefacts (spec, architecture, ADRs, standards) before asking blank.
Show, don't ask. When upstream artefacts already imply an answer, propose it as a pre-filled finding and ask for a yes / no confirmation rather than asking the user to fill in a blank.
not sure / skip triggers a sensible default, marked "(default applied — confirm later)" in the artefact, and a debt entry in this skill's debt file.

When KISS_AGENT_MODE=auto (or --auto), skip the questionnaire entirely: apply sensible defaults from upstream artefacts and log decisions to the parent agent's decision log.

Inputs

.kiss/context.yml
{context.paths.specs}/**/spec.md — functional + NFR source

Outputs

{context.paths.docs}/architecture/intake.md
{context.paths.docs}/architecture/intake.extract

Context Update

Does not mutate .kiss/context.yml.

Handoffs

kiss-tech-research reads intake to scope candidate evaluations.
kiss-adr reads constraints to frame the context of each ADR.
kiss-c4-diagrams reads the integration surface for the context diagram.

AI authoring scope

Does: ask the user structured questions, record answers, propose sensible defaults with "(AI proposal — confirm)".

Does not: interview stakeholders, assume anything about budget without the user stating it, commit the team to a stack.

Usage

<SKILL_DIR> = the integration's skills root (e.g. .claude/skills/ for Claude Code, .agents/skills/ for Antigravity / Codex, .cursor/skills/ for Cursor, .windsurf/workflows/ for Windsurf). Scripts live at <SKILL_DIR>/<skill-name>/scripts/….

bash <SKILL_DIR>/kiss-arch-intake/scripts/bash/draft-intake.sh --auto  # uses defaults + env vars
bash <SKILL_DIR>/kiss-arch-intake/scripts/bash/draft-intake.sh         # interactive

Answer keys

Key	Default
`AI_QA_TOP5`	empty (→ debt)
`AI_HARD_CONSTRAINTS`	empty
`AI_TEAM_SIZE_BAND`	`6-15`
`AI_PEAK_QPS`	empty
`AI_SLA_TARGET`	`99.9%`
`AI_DEPLOY_PREF`	`no-preference`

---name: kiss-arch-intakedescription: Captures architecture inputs — quality attributes ranking, hard constraints, team context, operational envelope, integration surface, deployment preferences — into a single intake artefact the architect works from. Use when starting system design, capturing requirements for an architecture, or before producing ADRs and C4 diagrams.---## User Input```text$ARGUMENTS```## Audience and tone (interactive mode)When `KISS_AGENT_MODE=interactive` (the default), assume the userhas **limited technical background and limited domain knowledge**— they may know basics but lack deep expertise in this skill'sarea. Run this skill as a guided questionnaire:- **One question at a time.** No walls of questions.- **Yes / no first.** Phrase so `yes`, `no`, `not sure`, or `skip` is a valid answer.- **Translate jargon, don't strip it.** Use the technical term but always pair it with a plain-English gloss the first time it appears.- **Choices, not blank fields.** When yes/no isn't enough, offer 2-4 lettered options (A/B/C/D) with one-line plain-language descriptions of the trade-off. Always include "Not sure — pick a sensible default".- **Always recommend.** State the option you would pick and why in one sentence so the user can reply "yes" / "ok" to accept. Pull defaults from upstream artefacts (spec, architecture, ADRs, standards) before asking blank.- **Show, don't ask.** When upstream artefacts already imply an answer, propose it as a pre-filled finding and ask for a yes / no confirmation rather than asking the user to fill in a blank.- **`not sure` / `skip` triggers a sensible default**, marked "(default applied — confirm later)" in the artefact, and a debt entry in this skill's debt file.When `KISS_AGENT_MODE=auto` (or `--auto`), skip the questionnaireentirely: apply sensible defaults from upstream artefacts and logdecisions to the parent agent's decision log.## Inputs- `.kiss/context.yml`- `{context.paths.specs}/**/spec.md` — functional + NFR source## Outputs- `{context.paths.docs}/architecture/intake.md`- `{context.paths.docs}/architecture/intake.extract`## Context UpdateDoes not mutate `.kiss/context.yml`.## Handoffs- `kiss-tech-research` reads intake to scope candidate evaluations.- `kiss-adr` reads constraints to frame the context of each ADR.- `kiss-c4-diagrams` reads the integration surface for the context diagram.## AI authoring scope**Does:** ask the user structured questions, record answers,propose sensible defaults with "(AI proposal — confirm)".**Does not:** interview stakeholders, assume anything about budgetwithout the user stating it, commit the team to a stack.## Usage> `<SKILL_DIR>` = the integration's skills root (e.g. `.claude/skills/`> for Claude Code, `.agents/skills/` for Antigravity / Codex,> `.cursor/skills/` for Cursor, `.windsurf/workflows/` for Windsurf).> Scripts live at `<SKILL_DIR>/<skill-name>/scripts/…`.```bashbash <SKILL_DIR>/kiss-arch-intake/scripts/bash/draft-intake.sh --auto # uses defaults + env varsbash <SKILL_DIR>/kiss-arch-intake/scripts/bash/draft-intake.sh # interactive```### Answer keys| Key | Default ||---|---|| `AI_QA_TOP5` | empty (→ debt) || `AI_HARD_CONSTRAINTS` | empty || `AI_TEAM_SIZE_BAND` | `6-15` || `AI_PEAK_QPS` | empty || `AI_SLA_TARGET` | `99.9%` || `AI_DEPLOY_PREF` | `no-preference` |

Frequently asked questions