Results for “team-workflow”

Design and evolve engineering team structures for fast flow of change using the Team Topologies framework, including Conway's law, four team types, three interaction modes, and cognitive load management.

Analyzes requirements and produces four artifact files: requirements, user stories, acceptance criteria, and business rules, with optional SRS workflow integration.

Use only for video game projects; route research, validation, roadmap, metrics, and launch work through the game pack

Creates or updates a canonical founder context document capturing company, product, market, team, and fundraising facts so downstream workflows operate on concrete data.

Analyzes requirements and produces four artifact files: requirements.md, user-stories.md, acceptance-criteria.md, and business-rules.md, with optional loading from SRS workflow artifacts.

Create, set up, or update the personal context portfolio: structured markdown files describing who you are, how you work, your teams, and your tool/ADO configuration. Runs the interview workflow for first-time setup and targeted edits for updates. Trigger this skill when the user asks to: set up their context, create or update their context portfolio, "create my IQ", "set up my IQ", edit their profile, add/remove a stakeholder, update ADO config, change team info, update pillars, or set up any plugin configuration. Trigger when another skill fails to find context (missing files or TODO markers) and needs context populated. Also trigger when the user mentions a context change in passing (e.g., "my manager changed", "we added someone to the team") to offer a context file update. Do NOT trigger for read-only questions like "who's on my team?" or "what's my ADO config?". Those are answered directly from the context files referenced in the loaded custom instructions; no skill is needed.