The initial application is to override the Content Spec pubsnumber value, or to provide one when one was not supplied.

So,

skynet build 1 --override pubsnumber=2

Something like that.

Rational: every time that you want to stage a new version of a book it requires a unique pubsnumber. At the moment the way to do that is:

1. Build the book
2. Edit the Book_Info.xml file, update pubsnumber
3. Stage book

Once we implement https://bugzilla.redhat.com/show_bug.cgi?id=748199 it could be:

1. Pull the --post content spec
2. Edit the pubsnumber value
3. Push the updated content spec
4. Build
5. Stage

With the ability to override the pubsnumber, the process will be:

0. Check most recent pubsnumber on stage
1. Build with override pubsnumber++
2. Stage