Merged
Conversation
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
…eration Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Add PromptAdherenceTask to full_plan_pipeline.py requires() dict and report.py requires() dict and run_inner(). Also fix bare Enum types in prompt_adherence.py Pydantic models to use Literal[...] as required by the codebase lint rules. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Incrementing integer prevents random ordering from the LLM. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
The report generator adds its own section header. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
The app now saves plan_raw.json (user prompt + date as JSON). SetupTask reads plan_raw.json and produces plan.txt from a template. This separates the raw user input from the formatted pipeline input. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Uses the raw user prompt directly, not the templated plan.txt. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Changed threshold from adherence <= 3 to adherence < 5 so partially_honored items appear in the Issues list. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Displays the formula below the overall score, e.g.: (5×5 + 4×4 + 5×3 + ...) / 250 = 94% Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Shows three lines: IMPORTANCE_ADHERENCE_SUM = (5×5 + 3×4 + ...) = 205 IMPORTANCE_SUM = 5 + 3 + ... = 41 OVERALL_ADHERENCE = IMPORTANCE_ADHERENCE_SUM / (IMPORTANCE_SUM × 5) = 205 / 205 = 94% Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Code blocks in sections like Prompt Adherence now render as <pre><code> instead of inline <code>, preserving line breaks. Co-Authored-By: Claude Opus 4.6 (1M context) <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
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
adherence_5(1-5 Likert) and categorized as Fully honored, Partially honored, Softened, Ignored, Contradicted, or Unsolicited caveatplan.txtintoplan_raw.json(raw user prompt + date as JSON) +SetupTask(template). Prompt adherence reads the raw user prompt directly, not the templated version.Motivation
PlanExe's pipeline has a "normalization bias" — each step nudges the plan toward what a reasonable project should look like. Over ~70 nodes the cumulative drift is significant. User-stated facts get overridden, requirements get softened, and the plan adds unsolicited feasibility studies. This step surfaces that drift so the user can see it at a glance.
Test plan
🤖 Generated with Claude Code