@ngxtm/devkit 2.1.0 → 3.0.1

package/workflows/documentation-management.md

@@ -1,121 +0,0 @@
-# Project Documentation Management
-
-### Roadmap & Changelog Maintenance
-- **Project Roadmap** (`./docs/development-roadmap.md`): Living document tracking project phases, milestones, and progress
-- **Project Changelog** (`./docs/project-changelog.md`): Detailed record of all significant changes, features, and fixes
-- **System Architecture** (`./docs/system-architecture.md`): Detailed record of all significant changes, features, and fixes
-- **Code Standards** (`./docs/code-standards.md`): Detailed record of all significant changes, features, and fixes
-
-### Automatic Updates Required
-- **After Feature Implementation**: Update roadmap progress status and changelog entries
-- **After Major Milestones**: Review and adjust roadmap phases, update success metrics
-- **After Bug Fixes**: Document fixes in changelog with severity and impact
-- **After Security Updates**: Record security improvements and version updates
-- **Weekly Reviews**: Update progress percentages and milestone statuses
-
-### Documentation Triggers
-The `project-manager` agent MUST update these documents when:
-- A development phase status changes (e.g., from "In Progress" to "Complete")
-- Major features are implemented or released
-- Significant bugs are resolved or security patches applied
-- Project timeline or scope adjustments are made
-- External dependencies or breaking changes occur
-
-### Update Protocol
-1. **Before Updates**: Always read current roadmap and changelog status
-2. **During Updates**: Maintain version consistency and proper formatting
-3. **After Updates**: Verify links, dates, and cross-references are accurate
-4. **Quality Check**: Ensure updates align with actual implementation progress
-
-### Plans
-
-### Plan Location
-Save plans in `./plans` directory with timestamp and descriptive name.
-
-**Format:** Use naming pattern from `## Naming` section injected by hooks.
-
-**Example:** `plans/251101-1505-authentication-and-profile-implementation/`
-
-#### File Organization
-
-```
-plans/
-├── 20251101-1505-authentication-and-profile-implementation/
-    ├── research/
-    │   ├── researcher-XX-report.md
-    │   └── ...
-│   ├── reports/
-│   │   ├── scout-report.md
-│   │   ├── researcher-report.md
-│   │   └── ...
-│   ├── plan.md                                # Overview access point
-│   ├── phase-01-setup-environment.md          # Setup environment
-│   ├── phase-02-implement-database.md         # Database models
-│   ├── phase-03-implement-api-endpoints.md    # API endpoints
-│   ├── phase-04-implement-ui-components.md    # UI components
-│   ├── phase-05-implement-authentication.md   # Auth & authorization
-│   ├── phase-06-implement-profile.md          # Profile page
-│   └── phase-07-write-tests.md                # Tests
-└── ...
-```
-
-#### File Structure
-
-##### Overview Plan (plan.md)
-- Keep generic and under 80 lines
-- List each phase with status/progress
-- Link to detailed phase files
-- Key dependencies
-
-##### Phase Files (phase-XX-name.md)
-Fully respect the `./docs/development-rules.md` file.
-Each phase file should contain:
-
-**Context Links**
-- Links to related reports, files, documentation
-
-**Overview**
-- Priority
-- Current status
-- Brief description
-
-**Key Insights**
-- Important findings from research
-- Critical considerations
-
-**Requirements**
-- Functional requirements
-- Non-functional requirements
-
-**Architecture**
-- System design
-- Component interactions
-- Data flow
-
-**Related Code Files**
-- List of files to modify
-- List of files to create
-- List of files to delete
-
-**Implementation Steps**
-- Detailed, numbered steps
-- Specific instructions
-
-**Todo List**
-- Checkbox list for tracking
-
-**Success Criteria**
-- Definition of done
-- Validation methods
-
-**Risk Assessment**
-- Potential issues
-- Mitigation strategies
-
-**Security Considerations**
-- Auth/authorization
-- Data protection
-
-**Next Steps**
-- Dependencies
-- Follow-up tasks

package/workflows/orchestration-protocol.md

@@ -1,16 +0,0 @@
-# Orchestration Protocol
-
-#### Sequential Chaining
-Chain subagents when tasks have dependencies or require outputs from previous steps:
-- **Planning → Implementation → Testing → Review**: Use for feature development
-- **Research → Design → Code → Documentation**: Use for new system components
-- Each agent completes fully before the next begins
-- Pass context and outputs between agents in the chain
-
-#### Parallel Execution
-Spawn multiple subagents simultaneously for independent tasks:
-- **Code + Tests + Docs**: When implementing separate, non-conflicting components
-- **Multiple Feature Branches**: Different agents working on isolated features
-- **Cross-platform Development**: iOS and Android specific implementations
-- **Careful Coordination**: Ensure no file conflicts or shared resource contention
-- **Merge Strategy**: Plan integration points before parallel execution begins

package/workflows/primary-workflow.md

@@ -1,45 +0,0 @@
-# Primary Workflow
-
-**IMPORTANT:** Analyze the skills catalog and activate the skills that are needed for the task during the process.
-**IMPORTANT**: Ensure token efficiency while maintaining high quality.
-
-#### 1. Code Implementation
-- Before you start, delegate to `planner` agent to create a implementation plan with TODO tasks in `./plans` directory.
-- When in planning phase, use multiple `researcher` agents in parallel to conduct research on different relevant technical topics and report back to `planner` agent to create implementation plan.
-- Write clean, readable, and maintainable code
-- Follow established architectural patterns
-- Implement features according to specifications
-- Handle edge cases and error scenarios
-- **DO NOT** create new enhanced files, update to the existing files directly.
-- **[IMPORTANT]** After creating or modifying code file, run compile command/script to check for any compile errors.
-
-#### 2. Testing
-- Delegate to `tester` agent to run tests and analyze the summary report.
-  - Write comprehensive unit tests
-  - Ensure high code coverage
-  - Test error scenarios
-  - Validate performance requirements
-- Tests are critical for ensuring code quality and reliability, **DO NOT** ignore failing tests just to pass the build.
-- **IMPORTANT:** make sure you don't use fake data, mocks, cheats, tricks, temporary solutions, just to pass the build or github actions.
-- **IMPORTANT:** Always fix failing tests follow the recommendations and delegate to `tester` agent to run tests again, only finish your session when all tests pass.
-
-#### 3. Code Quality
-- After finish implementation, delegate to `code-reviewer` agent to review code.
-- Follow coding standards and conventions
-- Write self-documenting code
-- Add meaningful comments for complex logic
-- Optimize for performance and maintainability
-
-#### 4. Integration
-- Always follow the plan given by `planner` agent
-- Ensure seamless integration with existing code
-- Follow API contracts precisely
-- Maintain backward compatibility
-- Document breaking changes
-- Delegate to `docs-manager` agent to update docs in `./docs` directory if any.
-
-#### 5. Debugging
-- When a user report bugs or issues on the server or a CI/CD pipeline, delegate to `debugger` agent to run tests and analyze the summary report.
-- Read the summary report from `debugger` agent and implement the fix.
-- Delegate to `tester` agent to run tests and analyze the summary report.
-- If the `tester` agent reports failed tests, fix them follow the recommendations and repeat from the **Step 2**.