Features/token improvements#25
Merged
Merged
Conversation
…ern to agent constraints and patterns, and refine evidence recording in implementation templates for clarity and efficiency.
… focus on relevant details
…g redundant details and improving structure across multiple files.
…y Implementation Pattern for improved task management and validation focus. Update tasks.md to streamline checkpoint references and validation methods.
…ncorporating foundation and architecture alignment, refining validation expectations, and clarifying readiness assessment criteria. Update relevant prompts and validation flows to reflect these changes.
…rn into constraints and workflows across clarify, finalize, and story agents. Update clarify.md to include detailed logging requirements for active blockers, ensuring clarity in the resolution process.
…ifying the Question Basis Pattern application and updating workflow state requirements for improved clarity and usability.
…ts in the Interactive Question Pattern and modifying the Clarification Log to include question intent and prompt text for improved context.
…rocesses, ensuring single item handling and improved section references in story artifacts. Update validation flows and metadata for consistency in source tracking and requirements.
…Quality Gate Pattern across implementation, review, and task planning. Update documentation to improve clarity on task execution, validation, and evidence recording. Ensure alignment with finalized briefs and source references for better traceability and accountability.
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
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.
This pull request updates the devspec agent guides, work item templates, and pattern documentation to clarify and enforce the "Minimum Necessary Implementation Pattern" across planning, implementation, and review stages. It also streamlines several templates for clarity and better artifact boundaries, and adds explicit guidance for diagrams and evidence logging.
The most important changes are:
Minimum Necessary Implementation Pattern Integration:
.github/agents/devspec.implement-task.agent.md,.github/agents/devspec.tasks.agent.md, and.github/agents/devspec.review.agent.md, requiring agents to avoid unnecessary code changes, dependencies, and complexity unless mandated by the finalized brief. This pattern is now referenced and enforced at all major devspec workflow stages.Task Planning and Execution Guidance:
.github/agents/devspec.tasks.agent.mdto default to 3-5 executable tasks, merge similar tasks, and require every task to have a concrete target, validation, and done condition. Standalone refactor or abstraction tasks are now disallowed unless required by the finalized brief.Evidence and Logging Improvements:
Template and Artifact Streamlining:
clarify.md,diagrams.md, andfinalize.mdtemplates to remove redundant instructions, clarify artifact boundaries, and reference upstream sources instead of duplicating content.Pattern Documentation:
.github/prompts/PATTERNS.md.These changes collectively enforce lean implementation, clearer artifact management, and more maintainable planning and review processes.