Spec brevity - #65
Merged
Merged
Spec brevity#65
Conversation
skapoor8
commented
Aug 31, 2026
skapoor8
left a comment
skapoor8
left a comment
Contributor
Author
There was a problem hiding this comment.
Inline comments only.
**Lean phase-file template** - Drop Requirements, Task Runner Commands, Design, and References boilerplate from `implementation/phase-N.md`; keep the lite Contract block and the doc-aware `## Doc Scope` section - Move process rules (brevity, build-system preservation, terse prose) into the executor agent definition so phase files stay task documents - Tighten the executor prompt: terse prose rule plus no direct build/test tool calls — discover recipes with the task skill instead - Restructure phase files to Introduction / Implementation / Validation / Deviations sections, with a validation line per task and a closing full-suite Validation + Deviations pair **Task-skill check wiring** - Replace recorded task-runner commands across planner, executor, updater, and agent-prompt wiring with `/task detect` + `/task list` discovery at execution time — never raw npm/pytest/go-test invocations - Update planning (new.md, guide.md, update.md), review, and validation (validation-loop.md, validation-prompt.md) checks to validate the lean shape and task-skill references instead of runner-command metadata - Keep runner commands out of bash fences in guide.md and out of validation prompt code blocks - Skip the code-completeness gate for lite plans (no `**Code:**` blocks) in new.md, review.md, and validation-loop.md
skapoor8
force-pushed
the
feature/spec-brevity
branch
from
August 31, 2026 09:27
124e935 to
7a0f15e
Compare
skapoor8
marked this pull request as ready for review
August 31, 2026 09:35
|
🎉 This PR is included in version 2.2.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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.
Intent
The spec skill's generated phase files were bloated. Each one carried three boilerplate blocks — Requirements, Task Runner Commands, and Design — that repeated the executor agent's own rules and the plan-level design. This branch trims phase files to four sections (Introduction, Implementation, Validation, Deviations), has executors discover build/test checks via the task skill at run time instead of recorded commands, and keeps the
--liteand--persistentflags working.Changes
implementation-template.mdnow produces only the four sections, with a one-line Introduction and no policy prose.--persistentplans keep a## Doc Scopesection right after the Introduction;--liteplans keep the**Contract (lite mode only…)**block.spec-executor.mdruns format → lint → typecheck → tests via the task skill (/task detect,/task list) — no recorded runner commands, no direct tool calls — and gains a terse-prose rule.validation-prompt.md,validation-loop.md,new.md,review.md,guide.md,update.md, plus the planner and updater agents. Validation now rejects old-shape boilerplate (Requirements process block, Task Runner Commands, Design sections) and rawnpm test-style invocations.--liteplans, whose tasks carry**Contract:**blocks instead of literal code. The requirements and tabulation gates still run.Validation
mise run testgreen on both committed phasesmise run skills:validategreen on both committed phasesgithub.event.beforeis non-zero, and the first push has an all-zero before.Future Work