feat: split Smith skill into task-scoped, directly invocable skills

Aperta
#52 0 commenti 0 reazioni 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 4 giorni

@dhl123 ci sta già lavorando.

Dal 10/9/2026.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

enhancement
Summary

Smith is currently exposed as a single smith skill. Every task — policy creation, test generation, policy testing, patching, Regal formatting, deduplication, cross-validation — is routed through one SKILL.md, which reads the user's intent and then delegates to the appropriate guide under opa_policy/ or test_generation/.

This has three costs:

  • No direct invocation. There is no way to say "run test generation" as a command. The user has to phrase it as natural language and rely on SKILL.md routing to the right guide.
  • The router is a bottleneck. Every new capability means another branch in SKILL.md, and the whole contract loads for even the narrowest task.

The proposal is to split Smith into task-scoped skills, each directly invocable — /smith-test, /smith-policy-creation, /smith-policy-testing, and so on. The underlying smith --flag CLI does not change. This is a restructuring of the skill layer only.

User story
User Story 1
  • As a: Smith user who knows exactly which stage I want to run
  • I want: to invoke that stage directly as its own skill, e.g. /smith-test
  • So that: I don't have to phrase my intent as prose and hope the router dispatches correctly
Acceptance Criteria
Scenario: Invoking a stage direct
  • Given the task-scoped skills are installed
  • When I invoke /smith-test
  • Then the test-generation workflow runs, and no other stage's instructions are loaded
Lingua principale
Python
Stelle
17
Fork
6
Merge medio
4g 31m
PR unite (30g)
16

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di IBM/smith

Tutte le issue di IBM/smith

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.