Launching today

vstack
Agent skills and writing rules for engineering leaders
1 follower
Agent skills and writing rules for engineering leaders
1 follower
Engineers use agent skills and linters to keep AI from writing bad code. Engineering managers still paste raw prompts into chat windows and get walls of corporate filler. vstack adapts the gstack and pstack skill pattern for engineering leadership and management workflows. It turns leadership heuristics and strict writing standards into reusable agent skills for executive communication, promo docs, talent cards, and 1:1 prep. Built in public and open-source.

Hi Product Hunt, I am Vikash, and I am working on vstack, an adaptation of the gstack and pstack skill pattern applied to engineering leadership and management workflows.
Engineers use agent skills and linters to keep AI from writing bad code. Engineering managers still paste raw prompts into chat windows and get walls of corporate filler. The goal with vstack is to turn leadership heuristics and writing standards into reusable agent skills for day-to-day management tasks, including executive communication, writing promos, reviewing docs, 1:1 prep, and talent cards.
It is early and actively a work in progress, with plenty of rough edges and missing pieces. Right now, my favorite part of the repo is the leadership writing house rules, which enforces clarity, bans passive voice and hedging, and forces every claim to pair with a concrete artifact or metric.
I would love feedback from other leaders and builders on the structure, what workflows belong in an agent skill versus leaving alone, and how you adapt agent workflows for non-coding tasks.