Orchestrate feature development from product specification through implementation, review, testing, and documentation.
npx skills add https://github.com/lalulali/vespyr --skill develop-lalulali
Please help me install this Agent Skill. Skill: develop Source: https://github.com/lalulali/vespyr/tree/main/.agents/skills/develop Command: npx skills add https://github.com/lalulali/vespyr --skill develop-lalulali
This Skill removes the chaos from feature development by turning strategy documents into a structured, gated workflow that guides a team from specification review through implementation, testing, verification, and documentation.
Ask the AI to guide the feature through the full develop workflow using the available spec, user stories, and repository artifacts.
High-intent search queries and answers about installing and using this skill.
A spec-to-production feature workflow requires validating product specs, coordinating architecture planning, executing parallel development, and enforcing quality gates before release. This structured approach removes chaos by guiding teams through explicit role handoffs from specification to documentation.
Setting up a kanban and code review workflow begins with validating product requirements, then activating execution planning to sequence dependencies. The workflow supports multi-developer parallel execution, code review, QA validation, and security audits before final product-manager signoff.
Yes, the workflow explicitly supports multi-agent collaboration and parallel development across multiple developers. It coordinates architecture decisions, backlog planning, and state-machine updates to synchronize parallel execution and quality checks.
Yes, strict verification of product specs is required before architecture planning begins. The workflow enforces verification gates on product specifications, execution plans, and quality checks before allowing implementation to proceed.
Release readiness gates include code review, QA validation, security audits, performance reviews, product-manager signoff, and documentation updates. Each gate must pass state-machine verification before the feature ships to production.
A gated spec-to-code workflow is not suitable for rapid prototyping or exploratory development lacking defined product specs. It requires explicit user stories, architecture decisions, and verification gates, making it too rigid for unstructured or speculative coding tasks.
lalulaliConvert product specifications into an execution plan with tasks, dependencies, and effort estimates.
mtsatryanAutomate production release management and rollback orchestration for Kubernetes deployments.
J03Fr0stAutomate CI/CD pipeline setup with GitHub Actions and quality gates.
cody-hutsonAutomate backlog management, sprint planning, quality gates, and release readiness checks.
