القائمة
Review Execution Notes — scan all task and phase session summaries for execution issues, command failures, and prompt deviations, then produce a consolidated report
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Run the Phase 3 static analysis, exploitation, and reporting orchestrator — analyzes JavaScript, exploits findings, and produces HTML+Markdown reports (confirmed & manual-validation) plus a reconciliation audit, with persistent false-positive/triage marking
Produce a unified, top-to-bottom markdown reference document for a selected phase (1, 2, or 3) — assembles the skill entry point, orchestrator pattern, task graph, shared procedures, and every task prompt in execution order
Knowledge Base Audit — read-only health check of knowledge/ (index accuracy, frontmatter completeness, stale entries, coverage gaps, ledger and profile health)
Knowledge Base Consolidation — merge duplicates, upgrade confidence, deprecate stale entries, and keep indexes accurate, one category at a time
Knowledge Base Harvest — convert raw task notes in knowledge/_staging/ into structured, reusable technique files, update indexes, and record technique outcomes in the effectiveness ledger
Run the Phase 1 login discovery orchestrator — identifies the login flow and authenticates all users defined in project.json
| name | VirtueWebAgent-review-execution-notes |
| description | Review Execution Notes — scan all task and phase session summaries for execution issues, command failures, and prompt deviations, then produce a consolidated report |
Scan all task session summaries and phase-level session summaries for execution issues, command failures, and prompt deviations reported by worker agents during this engagement.
Read every file that exists from these two groups:
Phase-level summaries (orchestrator session summaries):
state/phase1/session-summary.mdstate/phase2/session-summary.mdstate/phase3/session-summary.mdTask-level summaries (worker agent session summaries) — read all that exist under:
findings/tasks/phase1/findings/tasks/phase2/findings/tasks/phase3/For each directory under those paths, read session-summary.md if present.
To find all existing task-level summaries efficiently:
find findings/tasks -name "session-summary.md" | sort
Flag a task summary as having issues if it contains any of the following signals — not just a formal execution_notes bullet:
Explicit structured field:
execution_notes bullet that is non-empty and does not say "everything ran as expected" or "omit"Failure and error language (scan all free-form text in each summary):
Deviation and workaround language:
Incomplete or partial execution signals:
time_limit_reached: true in the corresponding output.json (check findings/tasks/<phase>/<task>/output.json if it exists alongside the session summary)re_auth_failed: trueerrors array in output.jsonWhen in doubt, include the entry. False positives are less costly than missed issues.
Produce a single consolidated report with these sections:
One paragraph: total task summaries read, how many had flagged content, how many were clean, and the top recurring issue (if any). If no session summaries exist yet, say so and stop.
For each task with any flagged content:
Task: <task directory name> (phase N)
execution_notes / free-form error text / output.json flag (whichever applies)Skip tasks with session summaries that contain none of the flag signals above.
Repeat the same format for the phase-level orchestrator summaries, attributing each issue to "Phase 1 orchestrator", "Phase 2 orchestrator", or "Phase 3 orchestrator".
Group recurring issues across tasks. For each group:
If a pattern has already been fixed in the prompts (i.e., the same fix was applied independently in multiple sessions), note that too.
List task names that had session summaries and no flagged content, so you can confirm coverage.
Write the report directly to the conversation — do not write it to a file unless the user asks. Keep section 2 terse: one or two lines per issue, not paragraphs. If section 2 is long (more than 40 entries), collapse it into the pattern table in section 4 and reference the count rather than listing every instance.