Split /spec-submit into /verify-submit and /create-runbook#29
Open
simsinght wants to merge 1 commit into
Open
Conversation
simsinght
force-pushed
the
split-verify-and-runbook-commands
branch
3 times, most recently
from
9b171ff to
8b303e4
Compare
Replace the single /spec-submit command with two focused flows and factor their shared logic into skills: - /verify-submit: you write the code; capture intent, key decisions, and acceptance criteria, no implementation steps. - /create-runbook: Aviator's agent writes the code from a spec with full implementation detail. - spec-submission skill: shared submission mechanics (message, AC review loop, specSubmit call, PR directive, error handling) both commands load. - acceptance-criteria skill: the shared AC quality rulebook. - /spec-submit becomes a deprecation stub pointing at the two commands. Both commands pass submission_type to specSubmit (verify vs runbook).
simsinght
force-pushed
the
split-verify-and-runbook-commands
branch
from
8b303e4 to
4ef2826
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Replaces the single
/spec-submitcommand with two focused flows, and factors their shared logic into skills so nothing is duplicated across the commands.Commands
/verify-submit— you write the code; Aviator verifies it against your intent. Captures intent, a free-form key-decisions/architecture record, and acceptance criteria, with no implementation steps. Primary flow./create-runbook— Aviator's agent writes the code from a spec with full implementation detail (scope, ordered steps)./spec-submit— now a short deprecation stub pointing at the two above.Skills (shared, single-sourced)
spec-submission— the submission mechanics both commands share: message style, the acceptance-criteria review loop with the user, thespecSubmitcall, the Runbook-URL PR directive, and error handling.acceptance-criteria— the AC quality rulebook.Each command file now carries only what's specific to its flow (spec shape +
submission_type) and loads both skills for the rest.What reviewers should know
The
spec-submissionskill is the shared mechanical half of the old/spec-submitcommand, generalized to be flow-neutral — the biggest chunk of the old command (the AC rulebook) is the separateacceptance-criteriaskill. The one new behavior is that both commands passsubmission_type(verify/runbook) tospecSubmit.