Add a new skill without creating debt
Apply a new-skill intake path that checks evidence, boundaries, hierarchy, and synonyms before adding a node.
urgent request A VP wants "autonomous-agent orchestration" added before a customer demo. The pressure is real, but the taxonomy has to survive after the demo. new-skill intake Evidence -> Boundary -> Placement -> Language Do not ask whether the phrase sounds modern. Ask whether it names a stable, reusable capability with enough evidence to track. Add phrase Fast now, expensive later. A stable concept enters the taxonomy, not just a phrase. Taxonomy responsiveness is not the same as taxonomy looseness. 01 Evidence 02 Boundary 03 Placement 04 Fresh case
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in