Skip to content
Discussion options

You must be logged in to vote

Correct: the lightweight /learn output is intentionally a staging area, not a guarantee that every extracted markdown becomes a first-class always-loaded skill.

The older /learn flow is basically:

  1. extract a reusable pattern
  2. save it as a learned artifact
  3. review it
  4. promote or rewrite the good ones into proper skill structure if they deserve permanence

So yes, end-user curation is part of the design.

If you want the more structured path, continuous-learning-v2 is the better direction now: observe -> instinct -> evolve / promote. That avoids turning every session artifact into a heavyweight skill too early.

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by affaan-m
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants