Replies: 1 comment
-
|
Tracking issue: #573 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Context
During a
/fix-prrun on PR #301, the workflow completed successfullybut had no mechanism to capture and post observations about the
night-market tooling itself (skills, agents, commands, hooks).
Observation
Current behavior: Workflows like
fix-pr,do-issue,execute-plancomplete their task and post results to the repo (comments, commits).
Observations about the tooling used during the workflow are lost
unless manually noted.
Desired behavior: Workflow completion steps (Step 6 in fix-pr,
final phase in do-issue, etc.) should include a reflection checkpoint:
"Did I observe friction, bugs, or improvement opportunities in the
tooling itself?" If yes, post to GitHub Discussions in the Learnings
category.
Existing Infrastructure
The
abstractplugin already has:post_learnings_to_discussions.py- posts to Learnings categoryauto_promote_learnings.py- promotes high-value learningsaggregate_learnings_daily.py- daily aggregation hookThe gap is wiring -- workflow commands don't call these scripts
at completion.
Proposed Improvement
Add a "tooling reflection" step to workflow completion phases:
post_learnings_to_discussions.pycommand UX friction
Affected Components
sanctum/skills/fix-pr-modules/steps/6-complete.mdsanctum/skills/do-issue/SKILL.mdsanctum/skills/workflow-improvement/SKILL.mdComplexity
Low (wiring existing infrastructure, no new code needed).
Defer to next branch -- current branch at RED ZONE (19K lines).
Source
/fix-workflowretrospective on/fix-prPR #301 run (2026-03-15).Beta Was this translation helpful? Give feedback.
All reactions