ask-bundle
Use when deciding which skill or flow fits your situation — the meta-router entry point for this bundle (direct specialist skills, multi-skill flows, local AFK issues), or when the request is vague and needs the quick-start menu. Routes then defers to the chosen specialist — does not execute the work itself.
- License 许可
- MIT
- 最近更新
- 2026-11-15
- Stars
- ★ 0
- Forks
- 1
01 前言 Front Matter
- name
- ask-bundle
- triggers
- [ "user", "model" ]
- description
- Use when deciding which skill or flow fits your situation — the meta-router entry point for this bundle (direct specialist skills, multi-skill flows, local AFK issues), or when the request is vague and needs the quick-start menu. Routes then defers to the chosen specialist — does not execute the work itself.
02 资源文件 3
- 参考文档modes/flows-detail.md12.5 KB
- 参考文档modes/orchestration-detail.md16.1 KB
- 参考文档PHASE-BOUNDARIES.md4.2 KB
03 SKILL.md 正文
Ask Bundle — the bundle router
One entry point: classify the objective, route to matching skills, keep control through verified completion. You don't remember every skill, so ask.
Detail docs: modes/orchestration-detail.md (full orchestration procedure, forbidden
actions, priority hierarchy), modes/flows-detail.md (verbose flow map),
PHASE-BOUNDARIES.md (context-handoff decision tree).
TL;DR
- Self-check: scope exactly, telegraphic, skills first, verify, no opinion.
- Classify objective; route directly to matching skill(s).
- Unclear objective ("ask-bundle"/"start") → quick-start menu via
ask_user_question. - 3+ steps →
todo_write; each step gets a VF (gate:/expect:/evidence:). qa-cire-runs every non-trivial gate on a clean checkout.- Run project verification (e.g.
python audit.py,pytest) before done.
Situation router
| Situation | Entry | Next |
|---|---|---|
| Assemble / expand a raw idea or prompt (OSINT + first principles + super-prompt) | montador-de-ideias |
→ project-orchestrator or grilling → planning |
| Build/change something | grilling (intent) or execution cadence if trivial |
→ planning spec→tickets → execution+testing → security (API/DB/secrets/infra) → code-review → gates → finishing-a-development-branch |
| Run AFK/unattended | execution execution (needs ready-for-agent issues) |
see AFK creation below |
| Hard/intermittent bug | debugging |
→ testing regression → architecture if no seam |
| CI failing | debugging ci mode |
|
| Triage incoming issues | intake |
→ execution |
| Large foggy multi-session effort | planning wayfinder |
→ spec → tickets → implement |
| Prototype to settle a question | prototype (via handoff) |
back to grilling/planning |
| Research/deep exploration | research |
feeds grilling/spec |
| Fact-check article/draft | fact-check |
→ humanizer on accepted fixes |
| De-AI-ify prose | humanizer |
|
| Need input from another person | planning questionnaire |
|
| Git merge/rebase conflict | git-workflows |
|
| Improve architecture/deep modules | architecture |
→ grilling if it generates an idea |
| Evolve skill/rule/hook/MCP | self-improvement |
→ writing-skills (one skill), devin-config (new capability) |
| Release/deploy/rollback | deploy |
→ gh, smoke tests |
| Security assessment | security |
→ execution for remediations |
| Data query/analysis/charts | data-analyst |
|
| UI/UX polish | impeccable |
→ a11y-audit/e2e-testing |
| Observability infra | observability-quality |
|
| API or DB design | api-spec or database |
→ execution |
| Performance/cost | performance or context-hygiene |
|
| Human-only procedure | wizard |
|
| Guided learning | teach |
|
| User owns design, agent teaches + writes | learn-mode |
off-ramp to execution once design approved |
| Write PR body/description | pr |
→ gh to create/update |
| Session retrospective / improve agent env | retro |
findings → continuous-improvement or issues |
| Husky/lint-staged pre-commit setup | setup-pre-commit |
|
| Set up repo for Devin | project-bootstrap |
|
| Not sure / no match | skill-discovery |
evaluate/install |
The main flow: idea → ship
montador-de-ideias(optional upstream) - when starting from a raw seed idea or prompt that needs journalistic OSINT market teardown, first-principles justification, atomic/modular hardening, contact-surface design, and an approved super-prompt in.devin/specs/.grilling(with-docs) — sharpen the idea by interview; stateful in.devin/CONTEXT.md+adr/. Stateless mode when no working directory.- Runnable question? → detour:
handoffout →prototype→handoffback. - Multi-session build?
- Yes →
planningspec → tickets (tracer bullets + blocking edges;.devin/scratch/<feature>/issues/on local tracker) →executionper ticket, clearing context between. Single focused session alternative:planningplan-doc →execution. - No →
executionimplement right here.
- Yes →
- Either way:
testingTDD inside →code-review(Standards+Spec) →securitywhen touching API/DB/secrets/endpoints/infra →gates→finishing-a-development-branch.
Context hygiene: keep 1–3 in one window until tickets are cut; each
implementation starts fresh. Approaching the smart zone (~150k) → compact at
the nearest phase boundary (PHASE-BOUNDARIES.md).
On-ramps
- Bugs/requests piling up →
intaketriage (issues you didn't create). - Something's broken →
debugging(tight feedback loop first). - Huge foggy effort →
planningwayfinder (decision-ticket map; hands off to spec when clear — never loop straight into implement). - Codebase health →
architecture(deepening opportunities generate ideas).
Vocabulary underneath
knowledge-modeling— domain language (.devin/CONTEXT.md, ADRs) + ontology validation.architecture— deep-module vocabulary (module/interface/depth/seam).ai-coding-dictionary— canonical AI-coding jargon.
Quick-start menu (vague request)
ask_user_question with 2–4 options:
- Assemble an idea/prompt or build/change something →
montador-de-ideias,grilling, orexecutioncadence - Improve a skill/rule/hook/MCP →
self-improvement - Debug/research →
debugging/research - Set up repo / run AFK →
project-bootstrap/executionafk
Quick AFK issue creation
- Confirm feature slug + objective.
- No spec →
grilling/planningspec →.devin/scratch/<slug>/spec.md. planningtickets → one file per ticketissues/<NN>-<slug>.md,Status: ready-for-agent,Blocked by:, acceptance checkboxes.- Verify files + DAG (
glob,read, parseStatus:/Blocked by:). executionexecution only on explicit user authorization.
Hard constraints (never violated)
- Safety + pinned
AGENTS.mdrules (2, 5, 7, 12-19, 21). - Verify with tools before asserting.
- Execute exactly what was asked, without opinion.
Then: usefulness → ease → quality of experience → technical coherence → performance.
Forbidden: deduce without tools; start non-trivial work without skill
discovery; mark completed without independent qa-ci PASS; override qa-ci
FAIL; push/commit with failing checks; AI signatures; display secrets;
destructive actions without confirmation; subagent_explore/paid models on
a free parent; execution without ready-for-agent issues; read/edit
tests/held-out/ from implementer context; reuse implementer shell for
qa-ci without reinstalling pinned deps.
Bundle context
- Validated CLI: see
validated_cli_versionindata/bundle-identity.json. - Models:
data/bundle-models.json— parentBUNDLE_DEFAULT_MODEL; subagentsBUNDLE_MAX_MODEL/BUNDLE_MEDIUM_MODEL, all free. No paid aliases on a free parent. - Issue tracker:
.devin/scratch/<feature>/+.devin/agents/issue-tracker.md,triage-labels.md. - Verification baseline:
python audit.py,python -m pytest. - Laya is NOT wired into agent routing — zero-shot accuracy was too low
to justify it (see plan
2026-09-22-laya-frentes-de-acao.md).extensions/laya-tools+implement-layaremain for per-project use.
04 同仓库更多 Skills
montador-de-ideias
Use when assembling, expanding, or elevating a raw project idea or initial prompt into an ultra-detailed, first-principles dossier and compiled master prompt with journalistic OSINT market research, Tech Lead and Staff Architect justifications, atomic and modular hardening/optimization, and high-impact contact surfaces.
git-github-adaptive-engineering
Use when any task touches git history, GitHub issues/PRs/releases/CI, repo governance, or branch and merge decisions. Runs the Fase Zero situational-awareness battery, picks one of five delivery flows via the adaptive decision engine, and enforces commit/PR information-density standards. Orchestrates the gh, git-workflows, github-actions, pr, and debug/finish skills.
adaptive-agenda-calendar-routine-engine
Use when planning or executing work across hours, days, weeks, or sprints. Turns the calendar into a strict time-blocked agenda (HH:MM-HH:MM blocks carrying a routine profile, expected inputs, and a handoff output artifact), runs the 5-stage cognitive flow (Radar and Hunt -> Triage plus Steve Jobs conception -> workbench manifest -> >=32-cycle loop -> Close plus Open-Minded Scrum), and unfolds macro calendar milestones into micro agenda blocks through extensions/gcal/wrapper.py.
demo
Use when demonstrating a skill in a fixture project.
duplicate-skill
Use when testing duplicate skill name detection.
duplicate-skill
Use when testing duplicate skill name detection.