Claude's features, remapped by level of delegation
Instead of listing Claude's features, rearranging them by level of delegation, that is, "how much of the work do I hand over?", gives six levels: asking, memory, deliverables, delegating work, automation and external connections, which correspond to Chat, Projects, Artifacts, Cowork and Claude Code, Skills, and Connectors respectively. The principle running through all of it is to ask for results, not answers: "Summarize this PDF" is a single intermediate task, while "Analyze it and take it all the way to a report for the team meeting" delegates the final deliverable. When the features get confusing, sort them by what repeats: materials and context mean a Project, the work process itself means Cowork or Claude Code, and writing rules mean a Skill. It also lays out a procedure: review the work plan Cowork puts forward first, then let it run, and once the output is ready, add a separate step asking it to check the output against the originals. You can hand over the work but not the responsibility, so a person has to make the final check on numbers, dates and amounts.
Key points
- A 6-level delegation ladder: asking → memory → deliverables → delegating work → automation → external connections
- Sort by what repeats — materials and context go to Projects, work processes to Cowork, rules to Skills
- A Project serves only one workspace; a Skill is reused in many places
- Right after the output, add "Compare this with the originals and check it" as a separate step
This is a note: my own write-up after reading several sources. It has no source link; events checked against a source are kept as records.