Guide teams through phased feature development from discovery to delivery.
npx skills add https://github.com/otahontas/nix --skill feature-dev-otahontas
Please help me install this Agent Skill. Skill: feature-dev Source: https://github.com/otahontas/nix/tree/main/home/configs/pi-coding-agent/skills/feature-dev Command: npx skills add https://github.com/otahontas/nix --skill feature-dev-otahontas
This Skill provides a repeatable, phase-driven approach to feature development, reducing miscommunication and rework by guiding teams from initial idea through delivery.
Initiate the feature-dev workflow for a new feature in your project, then follow each phase to produce a documented plan and track progress.
High-intent search queries and answers about installing and using this skill.
A structured feature development workflow guides teams through sequential phases: discovery, codebase exploration, clarifying questions, architecture design, implementation, quality review, and summary. This phase-driven approach reduces miscommunication and rework by enforcing a disciplined path from idea to delivery.
Implementing features across multiple files and teams requires a structured workflow with phases for discovery, codebase exploration, clarifying questions, architecture design, implementation, and quality review. This approach resolves ambiguities and coordinates cross-functional changes by enforcing a documented plan.
Yes, this structured feature development workflow supports refactoring large components and onboarding to new projects. The phased approach facilitates alignment across multiple files and teams by producing a documented plan and tracking progress throughout the implementation lifecycle.
The best way to resolve ambiguities before architecture design is to apply a structured workflow with dedicated discovery and clarifying questions phases. This ensures codebase exploration and requirement alignment happen before implementation begins, reducing rework and miscommunication.
Yes, this feature development approach works for cross-functional changes. It enforces a structured workflow with phases for discovery, architecture design, and quality review, specifically designed to coordinate changes that span multiple files and teams while reducing miscommunication.
7a336e6eDefine project scope, milestones, and roadmap with risk assessment.
anderson-0Coordinate software development sprints through planning, implementation, testing, review, deployment, and verification phases.
otahontasGuide teams through phased feature development from discovery to delivery.
aimskrCoordinate seven-phase feature development workflows with documentation and change management.
