Turn requirements into a repeatable delivery workflow

Product managers need to understand whether an existing specification covers a request, decide what should change and pass that change into implementation. Those activities can lose context when requirements, project knowledge and delivery tickets are handled separately.

I worked with PM stakeholders to turn those tasks into repeatable AI-assisted workflows. The goal was to make requirement work easier to carry into engineering, while keeping the project context and intended change clear.

I aligned the initial scope with PMs and designed and implemented requirement-check and requirement-update workflows. I added automatic ticket creation so the work could continue into an implementation task.

I developed the proof of concept, supported setup for a product team and iterated on the skills using PM feedback. I later added project-reference support so the workflow could work with the relevant project context.

The work extended beyond a single demonstration. In October 2026 I published six PM Tool skills to the company skills repository, with supporting scripts, references and installation guidance. The publication was merged, and file-integrity and isolated-installation checks passed.

The package included 69 evaluation cases. That is the size of the evaluation inventory, rather than a claim that all 69 cases passed or that 69 business workflows were adopted.

I supported PMs as they tried the workflows, collected issues and refined the skills. I also transferred knowledge to the IT team for continued workflow and skill updates.

This required thinking about how somebody else would install the package, select the project and continue using it after the initial setup. The installation guidance and handoff were part of the delivery, alongside the requirement and ticket-generation logic.

The concrete outcome was a published, reusable six-skill package with installation checks and supporting materials. The earlier POC and PM feedback work informed that package.

At the latest recorded checkpoint, PM-team installation in real requirement and bug workflows still needed validation, and one shared component needed standalone evaluation. Sustained independent use was the next adoption question, not an outcome already demonstrated.