b2b-backend-plan-update

You can automatically update QA results in a markdown plan by running this skill on a specified file path; it reads recent logs, extracts phase entries, and writes validated OK/NOK statuses into the QA summary table.

Yes, this plan update automation is designed for CI/CD pipelines. It reads the most recent logs from the ~/monitor-logs directory and restructures the markdown plan automatically after monitoring runs.

The process for reading monitor logs involves extracting phase entries from the specified markdown file, reading recent logs from ~/monitor-logs, validating the results, and writing updated per-phase outcomes and QA summary tables with correct statuses.

Yes, this QA validation tool requires monitoring logs to be stored in the ~/monitor-logs directory. It reads the most recent log files from this location to extract the latest QA outcomes for the plan update.

The markdown plan update handles OK and NOK statuses by validating the latest monitoring outcomes for each extracted phase entry, then writing the correct status into both the per-phase results and the overall QA summary table.