spike(framework): assess offline reliability of tool documentation references
Mantenedores costumam responder em até 1 dia
Ninguém assumiu esta issue ainda.
Avaliação
- Dificuldade
- 4/5
- Tempo estimado
- 3-5 dias
- Facilidade para iniciantes
- 30/100
- Tipo de issue
- Documentação
- Clareza
- Razoavelmente clara
- Status de atividade
- Ativa
- Domínio
- ai-infra-agents, documentation
Direção de pesquisa
Start by inventorying external vendor-documentation URLs in the installed skills, beginning with plugins/aidd-context/skills/06-agent-generate/references/tool-paths.md, 04-skill-generate/references/tool-write.md and 08-hook-generate/references/tool-paths.md, and classify each as citation, optional verification or required runtime lookup. Then run representative generation flows with documentation domains unreachable and record what the agent does. Done means a written inventory, reproduction results, and a recommendation with any follow-up issues scoped separately.
Escrita pelo modelo de indexação a partir do texto da issue.
Descrição
Problem
AIDD's tool-specific generation skills contain official documentation URLs for Kilo Code, Claude Code, Codex, OpenCode, Cursor, Copilot and other hosts. Source links are important for verifying platform contracts, but external documentation domains can be inaccessible in restricted enterprise networks.
Not every link creates a runtime dependency: many references already describe the contract locally. However, some instructions explicitly tell the agent to consult vendor documentation for information not recorded in the installed reference (for example, supported hook events). It is not yet established whether those workflows continue safely and reliably when the documentation cannot be reached.
This is a research spike, not a demonstrated product bug. The goal is to determine whether there is an actual offline-runtime gap and agree on an approach before proposing implementation changes.
Scope
- Inventory external vendor-documentation links in the installed AIDD skills, references, agents and rules; classify each as a citation, optional verification or potentially required runtime lookup.
- Trace representative generation flows for agents, skills, rules, commands/workflows and hooks across the supported hosts.
- Run reproducible restricted-network scenarios where vendor documentation access is unavailable, distinguishing cases with a locally sufficient contract from those that require missing information.
- Identify whether agents fail closed, invent unsupported facts, skip mandatory validation or block unnecessarily when a source is unavailable.
- Propose a framework-wide convention for locally sufficient execution contracts, optional source verification, evidence freshness and explicit handling of unknown or unverified behavior.
- Identify small follow-up implementation issues only where a reproducible gap exists, without requiring wholesale copies of vendor documentation.
Acceptance criteria
- A documented inventory identifies external documentation lookups and their role (citation / optional / required) with file references.
- Representative supported generation workflows are tested with documentation domains unreachable; reproduction steps and observed results are recorded.
- The report distinguishes actual runtime dependencies from harmless source links and identifies the behavior when a required fact cannot be verified.
- A proposed convention preserves official URLs, evidence provenance and verification dates while defining what must be available locally for reliable generation.
- Any limitations, security considerations and maintenance trade-offs (including documentation drift) are documented.
- The spike concludes with a clear recommendation and separately scoped follow-up issues, if warranted.
Prior art in this repo
- #618 — source-backed, dated and auditable tool references. Its requirement to avoid guessing tool behavior must remain intact.
- #1149 — deterministic framework-file validation; related, not a replacement for offline workflow testing.
- PR #992 — Kilo-native generation; example references:
plugins/aidd-context/skills/06-agent-generate/references/tool-paths.md: local agent mapping plus official vendor links.plugins/aidd-context/skills/04-skill-generate/references/tool-write.md: locally defined targets with sourced platform contracts.plugins/aidd-context/skills/08-hook-generate/references/tool-paths.md: requests external documentation checks for some hook events.
aidd_docs/README.mddescribes local marketplace installation for offline use; this spike examines workflows after installation, not marketplace download.
Out of scope
- Blocking or expanding PR #992 solely because it contains external documentation URLs.
- Removing official sources or replacing evidence-backed claims with unsourced assumptions.
- Vendoring entire provider documentation sites or introducing a live network requirement into every generation.
- Implementing a fallback, caching system or large-scale refactor before the investigation establishes a concrete need.
- Linguagem predominante
- TypeScript
- Estrelas
- 481
- Forks
- 45
- Merge médio
- 1d 13h
- PRs com merge (30d)
- 91
Preparar o ambiente
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Mais de ai-driven-dev/framework
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 86/100
ai-driven-dev/framework#1311 ·
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 79/100
ai-driven-dev/framework#1244 ·
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 78/100
ai-driven-dev/framework#1197 ·
Mantenedores costumam responder em até 1 dia
-
refactor(aidd-context): apply the new skill template to learnTalvez já em andamento @blafourcade assumiu há 3 dias. Aberta
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 72/100
ai-driven-dev/framework#1186 · 1 responsável ·
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 83/100
ai-driven-dev/framework#1163 · 1 comentário ·
Mantenedores costumam responder em até 1 dia
Todas as issues de ai-driven-dev/framework
Issues semelhantes
-
Dificuldade 1/5 1-3 horas Facilidade para iniciantes 87/100
Mantenedores costumam responder em até 1 dia
-
🛠️ dette technique
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 61/100
betagouv/mon-entreprise#4752 · 1 comentário ·
Mantenedores costumam responder em até 5 dias
-
type: bug
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 67/100
franciscoBSalgueiro/en-croissant#1111 ·
Mantenedores costumam responder em até 2 dias
-
area/providers type/feature version/v2
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 68/100
anomalyco/opencode#64845 · 1 comentário ·
Mantenedores costumam responder em até 1 dia
-
enhancement
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 72/100
Mantenedores costumam responder em até 1 dia