From intent-engineering
Scaffold Intent Engineering project config into a repo's .intense/ directory — ways-of-working, pattern policy (allow/block/approved), and architecture thresholds — so the team can tune the lenses and commit the settings. Stack-aware menu; idempotent (never clobbers existing config without confirmation). Use to set up or extend a project's .intense/ config.
How this skill is triggered — by the user, by Claude, or both
Slash command
/intent-engineering:ie-init [all | ways | patterns | thresholds] (blank = menu)[all | ways | patterns | thresholds] (blank = menu)The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Copies starter config templates from the plugin defaults into the project's `.intense/`
Copies starter config templates from the plugin defaults into the project's .intense/
directory so a team can declare its "ways of working" (lens toggles, conventions),
design-pattern policy (allow / block / pre-approved), and architecture thresholds — then
commit them. Once present, .intense/ supersedes the plugin defaults
(config-resolution.md) for every ie-* run in that repo.
If presenting the menu interactively in Claude Code, pre-load AskUserQuestion
(deferred tool): call ToolSearch with select:AskUserQuestion once before the menu.
If the harness has no blocking-question tool (ToolSearch returns nothing / call fails),
fall back to a numbered list and wait for the user's reply — never silently pick.
.intense/ at the repo root (current working directory's repo).Gemfile with rails, or config/application.rb, or app/models.ways-of-working.yaml, which is stack-agnostic, and note that pattern/threshold
packs for this stack aren't available yet.)Parse $ARGUMENTS: all, ways, patterns, thresholds select directly. Blank →
present the menu (multi-select):
| Option | File created | What it controls |
|---|---|---|
| Ways of working | .intense/ways-of-working.yaml | lens toggles, severity overrides, local conventions, confidence gate, report dir |
| Pattern policy | .intense/patterns.yaml | allowed / blocked / pre-approved design patterns, unknown-pattern handling |
| Thresholds | .intense/thresholds.yaml | architecture metric limits (fat model/controller, God object, service object, …) |
| All | all three | full config set |
Recommend All for a first run.
Source templates are ${CLAUDE_PLUGIN_ROOT}/config/defaults/<file>. For each selected
file:
mkdir -p .intense
SRC="${CLAUDE_PLUGIN_ROOT}/config/defaults/<file>"
DST=".intense/<file>"
if [ -e "$DST" ]; then echo "EXISTS: $DST"; else cp "$SRC" "$DST" && echo "CREATED: $DST"; fi
.intense/<file> without explicit confirmation — a
surprising clobber of committed team config is the failure mode to avoid (least
astonishment / no data loss). If a target exists, report it and ask whether to
overwrite, diff, or skip; default to skip.List what was created vs skipped. Then tell the user:
.intense/ to .gitignore.ie-* run in this repo now merges them over the plugin
defaults (project wins; lists replace unless extends: true)./ie-audit to see the current posture under the
new config.This skill only writes under .intense/. It never edits other project files, commits,
or pushes.
${CLAUDE_PLUGIN_ROOT}/references/config-resolution.md — how the scaffolded files are
merged and consumed${CLAUDE_PLUGIN_ROOT}/config/defaults/ — the source templatesnpx claudepluginhub davidteren/intent-engineering --plugin intent-engineeringProvides behavioral guidelines to reduce common LLM coding mistakes, focusing on simplicity, surgical changes, assumption surfacing, and verifiable success criteria.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.