ShipIt Team

Complete AI-powered software development workflow from analysis to deployment

An intelligent software development system with 7 specialized AI agents that guide you through business analysis, architecture design, development, project management, scrum management, test engineering, and UX design. Built for Claude Code with enterprise-grade practices and agile methodology.

🚀 Now available on NPM: npx shipit-team@latest install

What You Get

✅ Complete Development Lifecycle Coverage

• Business Analysis → Architecture Design → User Stories → Development → Testing → UX Design → Project Management

✅ 7 Specialized Agents

• Analyst - Business analysis and requirements gathering
• Architect - System architecture and technical design
• Developer - Implementation and coding
• PM (Product Manager) - Product strategy and roadmap
• SM (Scrum Master) - Sprint planning and agile facilitation
• TEA (Test Engineer) - Test architecture and quality assurance
• UX Designer - User experience and interface design

✅ Enterprise Development Practices

• Story-driven development with acceptance criteria
• Context-aware implementation using Story Context XML
• Test-first development and quality gates
• Architecture decision records
• Sprint planning and retrospectives
• Component-based test design

✅ Agile Methodology

• Sprint planning and backlog management
• User story creation and estimation
• Definition of Done (DoD) enforcement
• Continuous integration practices
• Team collaboration workflows

Features

• Story Context System: Comprehensive context management for accurate implementation

  • Story Context XML as single source of truth
  • Reduces hallucinations and rework
  • Links stories to architecture patterns and existing code
  • Ensures AC (Acceptance Criteria) compliance

• Specialized Agent Roles: Each agent has specific expertise and workflows

  • Switch seamlessly between agents as you progress through development
  • Clear role boundaries prevent scope creep
  • Context is preserved across agent interactions

• Workflow-Driven Development: Guided workflows for each phase

  • Analysis workflows for requirements gathering
  • Planning workflows for PRD and technical specs
  • Implementation workflows for story development
  • Review workflows for code quality and testing

• Progress Tracking: Automatic tracking of stories, epics, and sprints

  • Story status management (Approved, In Progress, Done)
  • Sprint burndown and velocity tracking
  • Epic completion monitoring

• Git Integration: Automatic commits and pushes to track development progress

• Test Architecture: Comprehensive testing framework with TEA agent

• Architecture Patterns: Catalog of proven patterns and decisions

Installation

ShipIt Team is available on NPM. No installation required - just run it directly in your project repository:

npx shipit-team@latest install

Or install globally:

npm install -g shipit-team
shipit-team install

The installer will:

1. Ask for your team and project configuration
2. Create .shipit-team/ directory with agents and workflows
3. Set up project structure for stories, epics, and documentation
4. Create workflow status tracking
5. Install Claude Code integration

Directory Structure Created

your-project-repo/
   .shipit-team/            # ShipIt Team installation
      _cfg/                # Configuration (preserved on updates)
      core/                # Core agents and tools
      development/         # Development module with agents
   .claude/commands/        # Claude Code commands
      shipit-team/
          analyst.md       # Launch business analyst agent
          architect.md     # Launch architect agent
          dev.md           # Launch developer agent
          pm.md            # Launch product manager
          sm.md            # Launch scrum master
          tea.md           # Launch test engineer
          ux.md            # Launch UX designer
          master.md        # Launch coordinator
   stories/                # User stories and epics
      backlog/             # Backlog items
      in-progress/         # Active development
      done/                # Completed stories
   docs/                   # Project documentation
      architecture/        # Architecture decisions and designs
      specifications/      # PRD and technical specs
   README.md               # Auto-updated progress tracker

Usage

Starting a New Project

In Claude Code, use the slash command:

/shipit-team:master

The master coordinator will:

1. Assess your project phase
2. Recommend which agent to work with
3. Guide you through the appropriate workflow
4. Track progress across the development lifecycle

Working with Different Agents

Business Analysis (Analyst Agent):

/shipit-team:analyst

• Conduct domain research
• Create product briefs
• Analyze requirements
• Define user journeys

Architecture Design (Architect Agent):

/shipit-team:architect

• Design system architecture
• Make technology decisions
• Create architecture decision records
• Define technical patterns

Development (Dev Agent):

/shipit-team:dev

• Implement user stories
• Follow Story Context XML
• Write tests
• Ensure AC compliance
• Code review

Project Management (PM Agent):

/shipit-team:pm

• Create product requirements documents
• Define epics and stories
• Manage product backlog
• Prioritize features

Scrum Management (SM Agent):

/shipit-team:sm

• Sprint planning
• Daily standup facilitation
• Sprint retrospectives
• Remove blockers

Test Engineering (TEA Agent):

/shipit-team:tea

• Design test architecture
• Create test plans
• Implement test automation
• Ensure quality gates

UX Design (UX Designer Agent):

/shipit-team:ux

• Create wireframes
• Design user interfaces
• Define interaction patterns
• User research

Story-Driven Development Workflow

1. Analysis Phase - Analyst gathers requirements
2. Planning Phase - PM creates PRD, Architect designs system
3. Story Creation - PM breaks down into epics and stories
4. Story Context - SM generates Story Context XML
5. Implementation - Dev implements following context
6. Testing - TEA validates quality
7. Review - Code review and DoD check
8. Done - Story marked complete

Viewing Progress

The root README.md is automatically updated with a progress table:

| Story ID | Title | Status | Assignee | Sprint | Epic | Link | |----------|-------|--------|----------|--------|------|------| | SHIP-001 | User Authentication | In Progress | Dev | Sprint 1 | Auth System | 📝 | | SHIP-002 | Login UI Design | Done | UX | Sprint 1 | Auth System | 📝 |

Click the 📝 link to navigate directly to the story directory.

Agent Communication Styles

Each agent has a distinct personality and communication style:

• Analyst (Name TBD): Research-focused, evidence-based, thorough
• Architect (Name TBD): Systems thinking, pattern-oriented, pragmatic
• Developer (Amelia): Implementation-focused, checklist-driven, precise
• PM (Name TBD): Product-focused, user-centric, strategic
• SM (Name TBD): Process-oriented, facilitator, blocker-removal
• TEA (Name TBD): Quality-focused, risk-aware, comprehensive
• UX Designer (Name TBD): User-focused, visual thinking, empathetic

Workflows Available

Analysis Workflows

• Domain Research
• Product Brief Creation
• Requirements Analysis

Planning Workflows

• PRD (Product Requirements Document)
• Technical Specification
• UX Design and Wireframes

Solutioning Workflows

• Architecture Design
• Solutioning Gate Check

Implementation Workflows

• Story Context Generation
• Dev Story Implementation
• Code Review
• Sprint Planning
• Sprint Retrospective

Testing Workflows

• Test Architecture Design
• Test Automation
• CI/CD Setup

Best Practices

1. Always start with Story Context - Dev agent requires Story Context XML before implementation
2. Follow the workflow sequence - Each phase builds on the previous one
3. Use the right agent for the task - Each agent has specific expertise
4. Maintain AC compliance - Every change maps to specific acceptance criteria
5. Tests pass 100% - Stories aren't done until all tests pass
6. Regular retrospectives - Use SM agent for continuous improvement

License

MIT

Contributing

Contributions welcome! Please open an issue or PR on GitHub.

Support

• Documentation: [Coming Soon]
• Issues: https://github.com/yourusername/ShipItTeam/issues
• Discussions: https://github.com/yourusername/ShipItTeam/discussions