Coordinate a software engineering team workflow across nine predefined stages.
npx skills add https://github.com/arxxyr/dotfiles --skill team-swe
Please help me install this Agent Skill. Skill: team-swe Source: https://github.com/arxxyr/dotfiles/tree/main/dot_agents/skills/team-swe Command: npx skills add https://github.com/arxxyr/dotfiles --skill team-swe
This Skill unit provides a comprehensive software engineering team setup with predefined roles and workflows, ensuring a maintainable, testable, and scalable delivery process.
Use the team-swe skill to set up a software engineering team for your project.
High-intent search queries and answers about installing and using this skill.
A structured software engineering team workflow coordinates predefined roles like Tech Lead, Dev, QA, and DevOps across stages from pre-research to closure. You need it for large projects requiring long-term maintenance, ensuring maintainable, testable, and observable delivery.
To set up a software engineering team workflow, use predefined roles and state machines to coordinate stages including intake, research, planning, execution, review, and archiving. This ensures your project maintains structured specification documents throughout the delivery lifecycle.
Yes, the software engineering team setup includes a lightweight mode for smaller projects. You can adapt the comprehensive workflow stages and predefined roles to operate with reduced overhead while still maintaining testable and reversible delivery standards.
Yes, the software engineering workflow includes an online fault SOP for incident handling and asset沉淀 for knowledge retention. These features ensure your team maintains observable and reversible delivery processes during operational disruptions.
A comprehensive software engineering workflow requires Tech Lead, Dev, QA, DevOps, and Security roles, with optional Doc or Perf roles. These predefined roles collaborate across pre-research, innovation, planning, execution, and closure stages.
Your team likely struggles with maintainable and observable delivery due to missing structured specification documents and undefined engineering workflows. Implementing a state machine-driven process across pre-research to closure stages enforces testable, deployable, and reversible outcomes.
OzeroHAXDefine project context, problem statement, and MVP boundaries.
GhostOf0daysAutomates observability and SRE workflows for quantitative trading systems.
barrydobsonAdvocate DevOps principles including CI/CD, IaC, automated testing, monitoring, and security scanning for delivery pipelines.
dralgorhythmAutomate agile ceremonies and backlog management for Scrum and Kanban teams.
