@forloop-cc/forloop-opencode-plugin-planner 2.2.1

package/CHANGELOG.md

@@ -0,0 +1,225 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [2.2.0] - 2026-03-25
+
+### Added - Sprint & Story API Enhancements
+
+#### New Sprint Tools
+- **forloopSprintCreate** - Create new sprint with dates and settings
+  - Arguments: title, description, startDate, endDate, isPrivate, organizationId
+  - Confirmation messages with sprint details
+- **forloopSprintUpdate** - Update sprint details
+  - Arguments: sprintId, title, description, startDate, endDate, isPrivate
+  - Partial updates supported
+- **forloopSprintDelete** - Delete sprint (with confirmation)
+  - Arguments: sprintId, confirm (required for safety)
+  - Warning message before deletion
+
+#### New Story Tools
+- **forloopStoryGet** - Retrieve story by ID
+  - Arguments: storyId
+  - Returns: story details, sprint info, assignee info, description
+
+#### Enhanced Story Create
+- **forloopStoryCreate** - Added missing server-compatible arguments:
+  - `status` - Initial story status (default: 'todo')
+  - `assigneeId` - User ID for assignment
+  - `assigneeType` - 'user' or 'agent' (default: 'user')
+  - `x`, `y` - Canvas position coordinates
+  - `zIndex` - Canvas layering order
+  - `templateId` - Template for story creation
+  - `metadata` - Additional JSON metadata
+
+#### API Client Updates
+- **CreateStoryRequest interface** - Extended with all server-compatible fields
+  - Matches server expectations in `server_lambda/src/controllers/storyController.ts`
+  - Proper type definitions for all optional fields
+
+---
+
+## [2.1.0] - 2026-03-24
+
+### Added - Phase 2a: Agents & Skills Integration
+
+#### Custom Agents
+- **forLoopPlanner** (Primary Agent) - Sprint planning specialist
+  - Tab-switchable primary agent for sprint workflows
+  - Guides users through sprint planning process
+  - Creates stories with INVEST criteria
+  - Invokes forLoopStoryEvaluator for estimates
+  - Auto-loads sprint-planning, story-creation, story-points skills
+  
+- **forLoopStoryEvaluator** (Subagent) - Story point estimation specialist
+  - Invoked via `@forLoopStoryEvaluator` mention
+  - 4-dimension analysis: complexity, effort, uncertainty, risk
+  - Provides confidence levels and reasoning
+  - Suggests splitting stories >5 points
+  - Calibration with historical stories
+
+#### Workflow Skills
+- **sprint-planning** skill - Structured sprint planning workflow
+  - Process flowchart with decision points
+  - Pre-planning and during-planning checklists
+  - Tool usage examples (sprint.list, sprint.get, story.create)
+  - Capacity planning calculations
+  - Common mistakes and fixes
+  
+- **story-creation** skill - User story best practices
+  - User story template (As a... I want... So that...)
+  - Given/When/Then acceptance criteria format
+  - INVEST criteria checklist
+  - Story sizing guidelines
+  - Epic decomposition examples
+  
+- **story-points** skill - Estimation framework
+  - 4-dimension estimation approach
+  - Points reference scale (0-10)
+  - Estimation techniques (triangulation, affinity mapping)
+  - Factors checklist (technical, knowledge, testing)
+  - Calibration examples by point value
+
+#### Configuration
+- Skill permissions system integration
+- Agent-specific permission overrides
+- Auto-loading skills based on permissions
+
+### Changed
+- Updated package.json to include `agent/` and `skills/` directories
+- Enhanced README.md with agents and skills documentation
+- Updated version to 2.1.0
+
+### Technical
+- Skills follow Superpowers pattern (frontmatter, flowcharts, checklists)
+- Agents follow OpenAgentsControl pattern (markdown with frontmatter)
+- Files distributed via npm/git package
+
+---
+
+## [2.0.0] - 2026-03-23
+
+### Added - Phase 2: AI Agent Integration
+
+#### New Tools
+- `forloopAgentSuggest` - Get AI-powered suggestions for story breakdowns, estimates, and planning
+- `forloopAgentBreakdown` - Automatically break down stories into actionable subtasks
+- `forloopAgentEstimate` - Get AI-suggested story points with rationale
+- `forloopAgentHistory` - View and filter conversation history with AI agents
+- `forloopAgentClear` - Clear conversation history (individual or bulk)
+
+#### Server-Side Features
+- New `/api/agents/suggestions` endpoint for context-aware AI suggestions
+- New `/api/agents/stories/:id/breakdown` for story task decomposition
+- New `/api/agents/stories/:id/estimate` for story point estimation
+- New `/api/agents/conversations` for conversation history management
+- Integration with existing WebSocket/Redis infrastructure for async AI responses
+- Support for conversation tracking by sprint and agent
+
+#### Agent Capabilities
+- **Breakdown suggestions**: Context-aware task decomposition based on story type
+  - Login/auth features → authentication middleware, password encryption
+  - Analytics features → data queries, visualization components
+  - Generic → database, API, UI, tests, documentation
+  
+- **Estimation**: Smart story point calculation
+  - Considers complexity, priority, description length
+  - Suggests points on Fibonacci-like scale (1-13)
+  - Provides estimation rationale
+  
+- **Conversation tracking**: Full history management
+  - Filter by sprint
+  - View request/response pairs
+  - Delete individual or bulk conversations
+
+### Changed
+- Updated plugin architecture to support Phase 2 features
+- Enhanced API client with new methods for agent operations
+
+### Technical
+- Added `agentSuggestionController.ts`
+- Added `conversationController.ts`
+- Added `agentSuggestionRoutes.ts`
+- Updated `app.ts` to register agent routes
+- Added type definitions for agent suggestions and conversations
+
+---
+
+## [1.0.0] - 2026-03-23
+
+### Added - Phase 1: Foundation & Authentication
+
+#### Core Features
+- `forloopTokenSet` - Set/update ForLoop API token
+- `forloopTokenGet` - Check if API token is configured
+- `forloopSprintGet` - Get sprint details with stories and files
+- `forloopSprintList` - List all accessible sprints
+- `forloopStoryCreate` - Create new stories
+- `forloopStoryUpdate` - Update existing stories
+- `forloopStoryDelete` - Delete stories
+- `forloopAgentQuery` - Query AI agents for analysis
+
+#### Server-Side
+- `OpencodeApiToken` database table with proper indexes
+- Token-based authentication middleware
+- API token validation with scope enforcement
+- RESTful endpoints at `/api/opencode/*`
+
+#### Infrastructure
+- Token storage in `~/.config/forloop/tokens.json`
+- Automatic sprint ID detection from git branches
+- Environment variable injection via `shell.env` hook
+- Installation scripts for local and global deployment
+
+#### Documentation
+- Comprehensive README.md
+- Installation scripts (5 methods)
+- Skill documentation
+- MIT License
+
+---
+
+## Version History
+
+| Version | Release Date | Phase | Features |
+|---------|--------------|-------|----------|
+| 0.1.0 | 2026-03-20 | Pre-Alpha | Initial prototype |
+| 1.0.0 | 2026-03-23 | Phase 1 | Foundation & Authentication |
+| 2.0.0 | 2026-03-23 | Phase 2 | AI Agent Integration |
+| 2.1.0 | 2026-03-24 | Phase 2a | Agents & Skills Integration |
+| 3.0.0 | TBA | Phase 3 | Autopilot & AWS |
+
+---
+
+## Semantic Versioning
+
+This project follows Semantic Versioning (SemVer):
+
+- **MAJOR** version for incompatible changes (e.g., breaking API changes)
+- **MINOR** version for backwards-compatible features
+- **PATCH** version for backwards-compatible bug fixes
+
+**Format:** `MAJOR.MINOR.PATCH` (e.g., 2.0.0)
+
+---
+
+## Upcoming Features (v3.0.0 - Phase 3)
+
+Planned for next release:
+
+- `forloop.autopilot.run` - Trigger autopilot development cycles
+- `forloop.autopilot.approve` - Approve/reject AI-generated change sets
+- `forloop.aws.deploy_lambda` - Deploy Lambda functions directly
+- `forloop.aws.create_resource` - Create AWS resources via AI
+- Enhanced WebSocket support for real-time AI responses
+- Multi-agent coordination features
+
+---
+
+**Unreleased** changes can be viewed on the `main` branch.
+
+[2.0.0]: https://github.com/forloop-cc/forloop-opencode-plugin/releases/tag/v2.0.0
+[1.0.0]: https://github.com/forloop-cc/forloop-opencode-plugin/releases/tag/v1.0.0

package/CODE_OF_CONDUCT.md

@@ -0,0 +1,77 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our community include:
+
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
+- Focusing on what is best not just for us as individuals, but for the overall community
+
+Examples of unacceptable behavior include:
+
+- The use of sexualized language or imagery, and sexual attention or advances of any kind
+- Trolling, insulting or derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or email address, without their explicit permission
+- Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official email address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at [INSERT CONTACT METHOD]. All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, during this period is allowed. Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org), version 2.0, available at https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity).
+
+For answers to common questions about this code of conduct, see the FAQ at https://www.contributor-covenant.org/faq. Translations are available at https://www.contributor-covenant.org/translations.

package/CONTRIBUTING.md

@@ -0,0 +1,176 @@
+# Contributing to ForLoop Plugin
+
+First off, thank you for considering contributing to the ForLoop Plugin! It's people like you that make the ForLoop Plugin such a great tool for the community.
+
+## Code of Conduct
+
+This project and everyone participating in it is governed by the [Code of Conduct](CODE_OF_CONDUCT.md). By participating, you are expected to uphold this code.
+
+## I have a question!
+
+Before creating an issue, check if:
+- The [README](README.md) answers your question
+- The [docs/](docs/) folder has relevant documentation
+- A similar issue already exists in the [issue tracker](https://github.com/forloop-cc/forloop-opencode-plugin/issues)
+
+If not, feel free to open an issue with the "question" label.
+
+## I want to report a bug!
+
+Bugs are tracked as [GitHub issues](https://github.com/forloop-cc/forloop-opencode-plugin/issues). Create an issue and provide the following information:
+
+- **Summary**: A clear, descriptive title
+- **Environment**: opencode version, Node.js version, OS
+- **Steps to Reproduce**: Detailed steps to reproduce the issue
+- **Expected behavior**: What you expected to happen
+- **Actual behavior**: What actually happened
+- **Logs**: Any relevant error messages or logs
+- **Additional context**: Screenshots, workarounds tried, etc.
+
+## I want to suggest a feature!
+
+Feature suggestions are welcome! Create an issue with:
+
+- **Summary**: Clear, descriptive title
+- **Problem statement**: What problem does this solve?
+- **Proposed solution**: How should it work?
+- **Alternatives considered**: Other approaches you've thought about
+- **Use cases**: Who will benefit from this feature?
+- **Additional context**: Examples, mockups, etc.
+
+## I want to contribute code!
+
+### Development Setup
+
+1. **Fork the repository** and clone it locally:
+```bash
+git clone https://github.com/YOUR_USERNAME/forloop-opencode-plugin.git
+cd forloop-opencode-plugin
+```
+
+2. **Install dependencies**:
+```bash
+npm install
+```
+
+3. **Set up local development**:
+```bash
+# Add the plugin to your local opencode.json pointing to this directory
+jq '.plugin |= (. // []) + ["file://'"$(pwd)"'"] | .plugin |= unique' \
+  opencode.json > opencode.json.tmp && mv opencode.json.tmp opencode.json
+```
+
+4. **Make your changes** following the coding conventions
+
+5. **Run tests**:
+```bash
+# Run all tests
+npm test
+
+# Run specific test suite
+npm run test:unit
+npm run test:integration
+```
+
+6. **Run type checking**:
+```bash
+npm run typecheck
+```
+
+### Pull Request Process
+
+1. **Create a branch** from `main`:
+```bash
+git checkout -b feature/your-feature-name
+```
+
+2. **Make your changes** following our coding standards:
+   - Write tests for new functionality
+   - Update documentation for user-facing changes
+   - Follow existing code style
+   - Add inline comments only when necessary (code should be self-documenting)
+
+3. **Commit your changes** with clear, descriptive messages:
+```bash
+git commit -m "feat: add new feature description"
+```
+
+We follow [Conventional Commits](https://www.conventionalcommits.org/):
+- `feat:` for new features
+- `fix:` for bug fixes
+- `docs:` for documentation changes
+- `style:` for formatting changes
+- `refactor:` for code refactoring
+- `test:` for adding tests
+- `chore:` for maintenance tasks
+
+4. **Push to your fork**:
+```bash
+git push origin feature/your-feature-name
+```
+
+5. **Open a Pull Request** against the `main` branch
+
+### PR Checklist
+
+Before submitting your PR, ensure:
+- [ ] Tests pass (`npm test`)
+- [ ] Type checking passes (`npm run typecheck`)
+- [ ] Code follows existing style
+- [ ] Documentation is updated
+- [ ] Commit messages are clear and follow conventions
+- [ ] PR description explains the change and why
+
+### Code Style
+
+- **TypeScript**: Strict mode enabled, explicit types
+- **Formatting**: Consistent indentation, meaningful variable names
+- **Error handling**: Return user-friendly error messages from tools
+- **Comments**: Only for complex logic, not for obvious code
+
+### Testing Guidelines
+
+- **Unit tests**: Test individual functions/components in isolation
+- **Integration tests**: Test API interactions (requires API token)
+- **Test naming**: Describe the expected behavior
+- **Test structure**: Arrange, Act, Assert pattern
+
+Example:
+```typescript
+describe('forloopSprintList', () => {
+  it('should list sprints successfully', async () => {
+    // Arrange
+    mockClient.listSprints.mockResolvedValue([...])
+    
+    // Act
+    const result = await tool.execute({}, {} as any)
+    
+    // Assert
+    expect(result).toContain('Sprints')
+  })
+})
+```
+
+## Releasing (Maintainers Only)
+
+1. Update `CHANGELOG.md` with new version and changes
+2. Bump version in `package.json`:
+```bash
+npm version patch  # or minor, or major
+```
+
+3. Push tags:
+```bash
+git push --follow-tags
+```
+
+4. Publish to npm:
+```bash
+npm publish
+```
+
+## Questions?
+
+Feel free to open an issue or reach out to the maintainers.
+
+Thank you for contributing! 🚀

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 ForLoop
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.