Did you know that the Software Craftsmanship Manifesto extends the Agile Manifesto?

Like this first line from the Software Craftsmanship Manifesto:

Not only working software,
  but also well-crafted software 

“Not only working software” is a reference to the Agile Manifesto:

Working software over comprehensive documentation

You can inline the references, so to speak, and end up with the following in order of the Agile Manifesto:

1. Instead of processes and tools, value individuals and interactions, but also a community of professionals.
2. Instead of comprehensive documentation, value working software that is also well-crafted.
3. Instead of contract negotiation, value customer collaboration, but also productive partnerships.
4. Instead of following a plan, value responding to change, while steadily adding value.

The order of the Software Craftsmanship Manifesto would be: 2, 4, 1, 3:

1. Instead of comprehensive documentation, value working software that is also well-crafted.
2. Instead of following a plan, value responding to change, while steadily adding value.
3. Instead of processes and tools, value individuals and interactions, but also a community of professionals.
4. Instead of contract negotiation, value customer collaboration, but also productive partnerships.

As a set of personal guidelines, I personally have put it this way:

I value customer collaboration
and productive partnerships
over contract negotiation.

I value working software that is well-crafted
over comprehensive documentation.

I value responding to change,
steadily adding value,
over following a plan.

I value individuals and interactions,
forming a community of professionals,
over processes and tools.