Skip to content

Rewrite domain-discovery to v3.0: task-focused skills, new phase ordering#5

Merged
LadyBluenotes merged 2 commits intomainfrom
add-meta-skills
Feb 25, 2026
Merged

Rewrite domain-discovery to v3.0: task-focused skills, new phase ordering#5
LadyBluenotes merged 2 commits intomainfrom
add-meta-skills

Conversation

@KyleAMathews
Copy link
Collaborator

Summary

Phase reordering (the big change)

Old: Read everything → draft domain map → interview maintainer
New: Quick scan → high-level interview → deep read → detail interview

The maintainer's mental model of developer tasks IS the skill map. The agent's job is to fill it with sourced content, not to independently derive the structure.

Output unit shift

  • Domains are now an intermediate conceptual grouping (4-7), not the final output
  • Skills are the output: task-focused, each matching a specific developer moment (10-20)
  • Skills emerge from the intersection of domains x developer tasks
  • YAML schema restructured: skills is top-level with domain reference, domains is a lightweight grouping

New skill types

  • Lifecycle skills (quickstart, go-live, migrate-from-X) — suggested when docs have the material
  • Composition skills — promoted from footnotes to full standalone skills when co-usage is consistent

Also includes (from v2.1 review fixes)

  • Removed phantom package_map.yaml references
  • Fixed Phase cross-reference numbering
  • Added skill_spec.md structural template
  • Clarified failure mode → Common Mistake mapping
  • Clarified cross-domain failure mode canonical location

Test plan

🤖 Generated with Claude Code

…ring

Major changes based on Electric SQL test run feedback (discussion #2):

Phase reordering:
- Phase 1: Quick scan (~10 min orientation) instead of exhaustive read
- Phase 2: High-level maintainer interview to extract task map FIRST
- Phase 3: Deep read informed by maintainer's mental model
- Phase 4: Detail interview (gap-targeted, AI-agent, composition)
- Phase 5: Finalize artifacts

Output unit shift:
- Domains are now an intermediate conceptual grouping, not the output
- Skills are the output: task-focused, each matching a developer moment
- Skills emerge from intersection of domains × developer tasks
- YAML schema restructured: skills are top-level with domain reference

New skill types:
- lifecycle skills (quickstart, go-live) suggested when docs support them
- composition skills promoted from footnotes to full skills

Other improvements:
- Monorepo heuristic: identify 2-3 core packages, read deeply
- GitHub issues fallback: FAQ.md, TROUBLESHOOTING.md when no web access
- tree-generator updated to consume new schema shape

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@LadyBluenotes LadyBluenotes merged commit e0e1114 into main Feb 25, 2026
1 of 4 checks passed
@LadyBluenotes LadyBluenotes deleted the add-meta-skills branch March 9, 2026 18:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants