A command verb is one assigned specific meaning by a technology, e.g. the word "edit" or "save" in a wiki is a command verb. So is "search", "login", etc.

extend into phrases

A verb phrase like "cancel edit" or "edit version as of date XXXX-XX-XX" elaborates the command verb unambiguously.

Many verbs are implicit, e.g. "Recent Changes" means "see recent changes".

A programming language permits construction of such verb phrases with specific meaning to an interpreter or a compiler.

set all name precedents

Command verbs set fixed name precedents, i.e. whatever meaning a verb might have in the content, it can't contradict the meaning assigned to it in all the controls of the user interface. Reflexivity is central to usability improvement.

Accordingly it is especially critical to set naming conventions correctly in the documentation of commands. Always conserve capitals when referring to command verbs - NEVER capitalize them. The seedwiki interface is a good example of how to reduce them, and mediawiki isn't bad either.

Managing command verbs in the same interface as all content attached to noun phrases, is a pre-requisite to a reflexive intranet - why would you talk about editing differently than you talk about anything else? Only if a variant power structure is implied, e.g. where admins rule trolls.

set precedents to document higher level actions

Reducing all conceivable actions in all technologies to verb phrases so they will integrate better with command verbs and will be supported in the same way makes a truly reflexive intranet - level 5 of the five levels of intranet.

Even wildly complex composite phrases like "draft plank" are documented and treated like low level command verbs when this is reached.