If a workflow requires some work pre or post apply or archive, there is currently no intuitive place to put them.
I can specify apply instructions in my custom schema, but I cannot do the same for when the other openspec workflow commands/skills are invoked.
One option is to overwrite the generated skills, but that is discouraged and brittle as it would overwrite upon openspec update command if upstream changes to the skills have been made.
The linked community schema superpowers-bridge hacks its way around this by invoking validate and archive within apply to simulate the ability to give post apply or inject custom archive instructions.
I take this as a sign of community demand.
I would to no apply such a hack and suggest having custom instruction hooks for the other core openspec workflow processing stages (commands/skills).
The pattern that I already see featured in custom schema files is the apply.instructions surface which could be extended as hooks to inject instructions to other openspec skills.
If a workflow requires some work pre or post apply or archive, there is currently no intuitive place to put them.
I can specify
applyinstructions in my custom schema, but I cannot do the same for when the other openspec workflow commands/skills are invoked.One option is to overwrite the generated skills, but that is discouraged and brittle as it would overwrite upon openspec update command if upstream changes to the skills have been made.
The linked community schema superpowers-bridge hacks its way around this by invoking validate and archive within apply to simulate the ability to give post apply or inject custom archive instructions.
I take this as a sign of community demand.
I would to no apply such a hack and suggest having custom instruction hooks for the other core openspec workflow processing stages (commands/skills).
The pattern that I already see featured in custom schema files is the
apply.instructionssurface which could be extended as hooks to inject instructions to other openspec skills.