feat: caveman compression + lifecycle interconnections for all skills#49
Merged
KailasMahavarkar merged 2 commits intomainfrom Apr 14, 2026
Merged
Conversation
…signer_verify_implementation Addresses two critical enforcement gaps from behaviour analysis: 1. VERIFICATION CLAIMS UNVERIFIED - Add Evidence Format section with concrete examples - Require actual command output pasted in message (not "I ran it") - Add red flags: "I ran tests" without output = no claim 2. DESIGN.md COMPLIANCE NOT AUTO-CHECKED - Replace manual grep checks with automated designer_verify_implementation tool - Require tool output as compliance evidence - Add red flags: manual checks miss edge cases, use the tool Changes: - Add "Evidence Format" section after "The Gate" with examples for tests, types, builds, MCP patterns - Clarify: "No output = no claim. Period." - Replace DESIGN.md Compliance Gate 10-row manual checklist with auto-invoke tool - Add Step 1 (Auto-Invoke), Step 2 (Show Output), Step 3 (Handle Failures) - Add 5 new red flags targeting common rationalizations around evidence and DESIGN.md Impact: Blocks two major verification loopholes. Moves compliance checking from optional manual steps to mandatory tool invocation. Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
- Compressed designer skill from 1640 → 650 lines (60% reduction) - Applied caveman compression: tables, arrows (→), dropped filler words - Added Lifecycle Integration sections to all 18 skills showing: * Agent workflow chains (website/frontend vs backend/infra) * Upstream dependencies * Downstream consumers * Reverse escalation paths * Execution mode routing (autonomous-mode | subagent-ops | engineering-discipline) - Made agent lifecycles explicit and enforceable - Preserved all meaning, context, MCP calls, and rules - Updated AGENTS.md with lifecycle rules
KailasMahavarkar
deleted the
feat/caveman-compression-lifecycle-interconnections
branch
KailasMahavarkar
added a commit
that referenced
this pull request
Apr 14, 2026
…#49) * fix: require verification evidence in message body and auto-invoke designer_verify_implementation Addresses two critical enforcement gaps from behaviour analysis: 1. VERIFICATION CLAIMS UNVERIFIED - Add Evidence Format section with concrete examples - Require actual command output pasted in message (not "I ran it") - Add red flags: "I ran tests" without output = no claim 2. DESIGN.md COMPLIANCE NOT AUTO-CHECKED - Replace manual grep checks with automated designer_verify_implementation tool - Require tool output as compliance evidence - Add red flags: manual checks miss edge cases, use the tool Changes: - Add "Evidence Format" section after "The Gate" with examples for tests, types, builds, MCP patterns - Clarify: "No output = no claim. Period." - Replace DESIGN.md Compliance Gate 10-row manual checklist with auto-invoke tool - Add Step 1 (Auto-Invoke), Step 2 (Show Output), Step 3 (Handle Failures) - Add 5 new red flags targeting common rationalizations around evidence and DESIGN.md Impact: Blocks two major verification loopholes. Moves compliance checking from optional manual steps to mandatory tool invocation. Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com> * feat: caveman compression + lifecycle interconnections for all skills - Compressed designer skill from 1640 → 650 lines (60% reduction) - Applied caveman compression: tables, arrows (→), dropped filler words - Added Lifecycle Integration sections to all 18 skills showing: * Agent workflow chains (website/frontend vs backend/infra) * Upstream dependencies * Downstream consumers * Reverse escalation paths * Execution mode routing (autonomous-mode | subagent-ops | engineering-discipline) - Made agent lifecycles explicit and enforceable - Preserved all meaning, context, MCP calls, and rules - Updated AGENTS.md with lifecycle rules --------- Co-authored-by: Claude Haiku 4.5 <noreply@anthropic.com>
KailasMahavarkar
added a commit
that referenced
this pull request
Apr 14, 2026
…#49) * fix: require verification evidence in message body and auto-invoke designer_verify_implementation Addresses two critical enforcement gaps from behaviour analysis: 1. VERIFICATION CLAIMS UNVERIFIED - Add Evidence Format section with concrete examples - Require actual command output pasted in message (not "I ran it") - Add red flags: "I ran tests" without output = no claim 2. DESIGN.md COMPLIANCE NOT AUTO-CHECKED - Replace manual grep checks with automated designer_verify_implementation tool - Require tool output as compliance evidence - Add red flags: manual checks miss edge cases, use the tool Changes: - Add "Evidence Format" section after "The Gate" with examples for tests, types, builds, MCP patterns - Clarify: "No output = no claim. Period." - Replace DESIGN.md Compliance Gate 10-row manual checklist with auto-invoke tool - Add Step 1 (Auto-Invoke), Step 2 (Show Output), Step 3 (Handle Failures) - Add 5 new red flags targeting common rationalizations around evidence and DESIGN.md Impact: Blocks two major verification loopholes. Moves compliance checking from optional manual steps to mandatory tool invocation. Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com> * feat: caveman compression + lifecycle interconnections for all skills - Compressed designer skill from 1640 → 650 lines (60% reduction) - Applied caveman compression: tables, arrows (→), dropped filler words - Added Lifecycle Integration sections to all 18 skills showing: * Agent workflow chains (website/frontend vs backend/infra) * Upstream dependencies * Downstream consumers * Reverse escalation paths * Execution mode routing (autonomous-mode | subagent-ops | engineering-discipline) - Made agent lifecycles explicit and enforceable - Preserved all meaning, context, MCP calls, and rules - Updated steering docs with lifecycle rules --------- Co-authored-by: Claude Haiku 4.5 <noreply@anthropic.com>
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.
Summary
Compressed all skills using caveman-style wording and added explicit lifecycle interconnections across the entire skill system.
Changes
Caveman Compression
→) for cause/effect relationshipsLifecycle Integration (All 18 Skills)
Added Lifecycle Integration sections showing:
Key Workflow Chains Now Explicit
Website/Frontend Agent:
Backend/Infra Agent:
Execution Options (chosen at forge-plan handoff):
autonomous-mode→ full auto, stops only on failuresubagent-ops→ fresh agent per task, two-stage reviewengineering-discipline→ manual with phase gatesBenefits
Files Changed
Testing