You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Provide a short workflow for authoring one validated skill #238
Scaffold routes maintainers through domain discovery, tree generation, and skill generation with intermediate artifacts and review stops. The existing lightweight branch still requires loading a large discovery file.
Evidence
The first three shipped meta-skills total 90,780 bytes. Domain discovery has a lightweight path, but scaffold still prescribes the three-stage sequence.
Verified against main at 206e987 (@tanstack/intent 0.3.8), Node v24.12.0 on macOS arm64. Tests used installed dependencies and synthetic local fixtures.
Acceptance criteria
Define a short path from one maintainer task to one validated SKILL.md.
Load optional planning schemas, tables, and extensive examples only when needed.
Keep the full-library authoring path available without forcing its artifacts onto the one-skill path.
Demonstrate the short path on one small package and record the context it requires.
Generated skills continue to satisfy existing validation and remain grounded in package source.
Scope and priority
Priority: Medium. Type: feature design.
Follow-up design, independent from repairing meta-skill validation. Do not delete advanced workflows or require a new artifact schema without a concrete need.
Maintainer decision, 2026-09-11: keep the three cumulative planning records required by #258, including for one-skill authoring tasks. Leave this issue open; an artifact-free authoring path is not part of the current stack.
#258 already provides focused task routing and conditional references. The remaining artifact-free criterion conflicts with the current authoring procedure, which requires domain_map.yaml, skill_spec.md, and skill_tree.yaml for every authoring batch or update. The earlier walkthrough explicitly predates that requirement, so it does not establish an artifact-free path in the current workflow.
No second authoring implementation was added. Public documentation remains in #259.
Activity
LadyBluenotes commentedon Sep 11, 2026
Maintainer decision, 2026-09-11: keep the three cumulative planning records required by #258, including for one-skill authoring tasks. Leave this issue open; an artifact-free authoring path is not part of the current stack.
#258 already provides focused task routing and conditional references. The remaining artifact-free criterion conflicts with the current authoring procedure, which requires domain_map.yaml, skill_spec.md, and skill_tree.yaml for every authoring batch or update. The earlier walkthrough explicitly predates that requirement, so it does not establish an artifact-free path in the current workflow.
No second authoring implementation was added. Public documentation remains in #259.