Lintel on GitHub Copilot. Generated from skills/research/SKILL.md; edit the canonical file, then run
li-copilot init.
- Resource root:
../../.. from this skill's base directory (the Lintel source with bin/,
lib/, skills/). Write plans, state and evidence into the working repository's .claude/
tree, never into the resource root.
- Skill-relative paths: this skill's own
scripts/, references/ and data/ folders (and a
<base> that the workflow defines as its own directory) mean
../../../skills/research/ in the Lintel source, not this generated folder.
${LINTEL_SKILLS_DIR:-skills} means the skills root, ../../../skills. A bin/li-run step
runs in the working repository, so use $LINTEL_SKILLS_DIR/research/ there.
- Shell steps: run Bash snippets with Bash (Git for Windows'
bash.exe on Windows, never
System32\bash.exe). Save a snippet to a temporary .sh file and run
bash "<resource root>/bin/li-run" <file>; it prepares LINTEL_SOURCE_ROOT, LINTEL_REPO_ROOT
and the profile context.
- Tools: Read=
view, Write=create, Edit=edit, Bash=bash/powershell, Grep=grep,
Glob=glob, AskUserQuestion=ask_user, TodoWrite=the plan checklist, Task or a named role=task
with that custom agent, WebFetch=web_fetch.
- Other Lintel workflows are native skills: invoke
/li-<name> rather than reading their
files. Named roles such as CodeReviewer are custom agents.
Research
A compatibility shortcut for exactly one route:
/li-cycle --mode research-dive
Follow the cycle research-dive preset. It runs SENSE, DEFINE and
DISCOVER and skips PLAN, BUILD, REVIEW, SHIP and CAPTURE. This entry adds no phase
engine, mode or flag of its own; forward only the operator's research scope.
- DEFINE frames the research question and source boundary. It does not require an
approved implementation design, and its findings are not implementation approval.
- Keep the selected work, scope and data-handling boundaries. Read-only research is not
a policy exemption; the active pack's read and data rules still apply.
- Write research or discover artifacts only where writing is authorized. When all
writes are forbidden, report findings in the conversation instead.
- Ask only for missing source access or material research questions; do not ask again
whether to do the research the operator requested.
Implementation afterwards needs its own scoped DEFINE/PLAN approval, for example
/li-cycle --from PLAN on the selected design.
1---2name: li-research3description: Use when the operator wants to understand a domain, codebase or option space before committing to implementation. Runs the research-dive cycle — SENSE, DEFINE and DISCOVER — and stops with sourced findings, never BUILD or SHIP.4metadata:5 source: https://skillmd.com/skills/jokerman89/li-research6---78> **Lintel on GitHub Copilot.** Generated from `skills/research/SKILL.md`; edit the canonical file, then run9> `li-copilot init`.10> - **Resource root:** `../../..` from this skill's base directory (the Lintel source with `bin/`,11> `lib/`, `skills/`). Write plans, state and evidence into the working repository's `.claude/`12> tree, never into the resource root.13> - **Skill-relative paths:** this skill's own `scripts/`, `references/` and `data/` folders (and a14> `<base>` that the workflow defines as its own directory) mean15> `../../../skills/research/` in the Lintel source, not this generated folder.16> `${LINTEL_SKILLS_DIR:-skills}` means the skills root, `../../../skills`. A `bin/li-run` step17> runs in the working repository, so use `$LINTEL_SKILLS_DIR/research/` there.18> - **Shell steps:** run Bash snippets with Bash (Git for Windows' `bash.exe` on Windows, never19> `System32\bash.exe`). Save a snippet to a temporary `.sh` file and run20> `bash "<resource root>/bin/li-run" <file>`; it prepares `LINTEL_SOURCE_ROOT`, `LINTEL_REPO_ROOT`21> and the profile context.22> - **Tools:** Read=`view`, Write=`create`, Edit=`edit`, Bash=`bash`/`powershell`, Grep=`grep`,23> Glob=`glob`, AskUserQuestion=`ask_user`, TodoWrite=the plan checklist, Task or a named role=`task`24> with that custom agent, WebFetch=`web_fetch`.25> - **Other Lintel workflows** are native skills: invoke `/li-<name>` rather than reading their26> files. Named roles such as `CodeReviewer` are custom agents.2728# Research2930A compatibility shortcut for exactly one route:3132```33/li-cycle --mode research-dive34```3536Follow the [cycle](../../../skills/cycle/SKILL.md) research-dive preset. It runs SENSE, DEFINE and37DISCOVER and skips PLAN, BUILD, REVIEW, SHIP and CAPTURE. This entry adds no phase38engine, mode or flag of its own; forward only the operator's research scope.3940- DEFINE frames the research question and source boundary. It does not require an41 approved implementation design, and its findings are not implementation approval.42- Keep the selected work, scope and data-handling boundaries. Read-only research is not43 a policy exemption; the active pack's read and data rules still apply.44- Write research or discover artifacts only where writing is authorized. When all45 writes are forbidden, report findings in the conversation instead.46- Ask only for missing source access or material research questions; do not ask again47 whether to do the research the operator requested.4849Implementation afterwards needs its own scoped DEFINE/PLAN approval, for example50`/li-cycle --from PLAN` on the selected design.