Provide a short workflow for authoring one validated skill

まず packages/intent/src/commands/scaffold.ts と domain-discovery SKILL.md を読み、既存の scaffold シーケンスと軽量な discovery パスを比較します。提案する短いパスを 1 つの小さなパッケージで実演し、必要なコンテキストを記録します。短いパスと完全なライブラリのパスの両方が引き続き利用でき、生成された skills が既存のバリデーションに合格し、パッケージのソースに基づいた状態を維持できれば完了です。

Problem

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.

Sources: scaffold, domain discovery.

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.