@silverassist/agents-toolkit 2.0.0

package/templates/shared/prompts/analyze-ticket.prompt.md

@@ -0,0 +1,63 @@
+---
+agent: agent
+description: Analyze a Jira ticket without creating branches or making changes
+---
+
+# Analyze Jira Ticket
+
+Analyze Jira ticket **{ticket-id}** and provide a comprehensive assessment without making any code changes.
+
+## Prerequisites
+- Atlassian MCP connection is required
+- Reference: `.github/prompts/_partials/jira-integration.md`
+
+## Steps
+
+### 1. Verify Jira Access
+- Use `getAccessibleAtlassianResources` to confirm connectivity
+- Get the correct cloud ID for subsequent calls
+
+### 2. Fetch Ticket Details
+- Use `getJiraIssue` with ticket **{ticket-id}**
+- Request fields: `summary`, `description`, `status`, `issuetype`, `priority`, `assignee`
+- Read all comments for additional context
+
+### 3. Analyze Codebase Impact
+- Search the codebase for related components
+- Identify files likely to be modified
+- Check for existing implementations or patterns
+
+### 4. Generate Report
+
+Provide the following structured analysis:
+
+#### 📋 Summary
+Brief overview of what needs to be done.
+
+#### ✅ Acceptance Criteria
+- [ ] Criterion 1
+- [ ] Criterion 2
+- [ ] Criterion 3
+
+#### 🔍 Technical Impact
+| Area | Files/Components | Impact Level |
+|------|------------------|--------------|
+| Components | list | High/Medium/Low |
+| Actions | list | High/Medium/Low |
+| Types | list | High/Medium/Low |
+
+#### 📊 Complexity Estimate
+- **Level**: Simple / Medium / Complex
+- **Estimated time**: X hours/days
+- **Reasoning**: Why this complexity level
+
+#### ⚠️ Risks & Blockers
+- Risk 1: Description and mitigation
+- Risk 2: Description and mitigation
+
+#### 🔗 Related
+- Related tickets or documentation
+- Similar implementations in codebase
+
+## Output Format
+Present findings in a clear, structured format that can be referenced during implementation.

package/templates/shared/prompts/create-plan.prompt.md

@@ -0,0 +1,118 @@
+---
+agent: agent
+description: Create a detailed implementation plan for a feature
+---
+
+# Create Implementation Plan
+
+Create a detailed implementation plan for: **{feature-description}**
+
+## Prerequisites
+- Reference: `.github/prompts/_partials/documentation.md` for plan template
+- Reference: `AGENTS.md` for agent workflow conventions
+- Reference: `.github/copilot-instructions.md` (if present) for additional project conventions
+
+## Steps
+
+### 1. Analyze Request
+- Break down the feature into components
+- Identify affected areas of the codebase
+- Search for related implementations
+
+### 2. Research Current State
+- Read relevant source files
+- Understand current architecture
+- Document existing patterns
+
+### 3. Create Planning Document
+
+Save to: `docs/{feature-name}-plan.md`
+
+Include these sections:
+
+---
+
+# {Feature Name} Implementation Plan
+
+## Problem Statement
+What problem are we solving? Why is this change needed?
+
+## Current Architecture
+- How does the current system work?
+- What components are involved?
+- What are the limitations?
+
+## Proposed Changes
+
+### Overview
+High-level description of the solution.
+
+### Technical Approach
+- Component 1: Changes needed
+- Component 2: Changes needed
+- New components to create
+
+### API Changes
+If applicable, document any API changes.
+
+## Risk Assessment
+
+| Risk | Probability | Impact | Mitigation |
+|------|-------------|--------|------------|
+| Risk 1 | Low/Med/High | Low/Med/High | Strategy |
+| Risk 2 | Low/Med/High | Low/Med/High | Strategy |
+
+## Phase Breakdown
+
+### Phase 1: {Phase Name}
+**Objective**: What this phase accomplishes
+
+- [ ] Task 1
+- [ ] Task 2
+- [ ] Task 3
+
+**Validation**: How to verify this phase is complete
+
+### Phase 2: {Phase Name}
+**Objective**: What this phase accomplishes
+
+- [ ] Task 1
+- [ ] Task 2
+
+**Validation**: How to verify this phase is complete
+
+## Testing Strategy
+
+### Unit Tests
+- Test case 1
+- Test case 2
+
+### Integration Tests
+- Scenario 1
+- Scenario 2
+
+### Manual Testing
+- Steps to manually verify
+
+## Rollback Plan
+How to revert changes if issues arise.
+
+## Dependencies
+- External dependencies
+- Internal dependencies
+- Team coordination needed
+
+---
+
+### 4. Commit Plan
+
+```bash
+git add docs/{feature-name}-plan.md
+# Prefer Jira-prefixed commit messages when ticket ID is known
+git commit -m "{ticket-id}: Add {feature-name} implementation plan"
+# Fallback when no ticket ID is available:
+# git commit -m "docs: Add {feature-name} implementation plan"
+```
+
+## Output
+The planning document at `docs/{feature-name}-plan.md` ready for implementation.

package/templates/shared/prompts/create-pr.prompt.md

@@ -0,0 +1,139 @@
+---
+agent: agent
+description: Create a pull request for the current branch
+---
+
+# Create Pull Request
+
+Create a pull request for the current branch linked to Jira ticket **{ticket-id}**.
+
+## Prerequisites
+- Run `prepare-pr` first to ensure code is ready
+- Reference: `.github/prompts/_partials/pr-template.md`
+- Reference: `.github/prompts/_partials/git-operations.md`
+- Reference: `.github/prompts/_partials/jira-integration.md`
+
+## Steps
+
+### 1. Verify Current State
+
+```bash
+git branch --show-current
+git status
+```
+
+Verify:
+- Branch follows convention: `feature/{ticket-id}-*` or `bugfix/{ticket-id}-*`
+- All changes are committed
+- Not on protected branch
+
+### 2. Review Changes
+
+```bash
+BASE_BRANCH=$(node -e "try{const c=require('./.agents-toolkit.json');console.log(c.pr?.targetBranch||c.git?.defaultBranch||'main')}catch{console.log('main')}")
+git diff "$BASE_BRANCH" --name-only
+```
+
+- Reuse `BASE_BRANCH` in all subsequent steps
+- Summarize the changes made
+- Identify breaking changes or migrations
+
+### 3. Read Jira Ticket
+
+Fetch ticket **{ticket-id}** details:
+- Get summary for PR title
+- Extract acceptance criteria
+- Get any context from comments
+
+### 4. Run Final Validations
+
+```bash
+npm run lint --if-present
+npm run type-check --if-present
+if [ -f tsconfig.json ]; then npx tsc --noEmit; fi
+npm run test --if-present
+npm run build --if-present
+```
+
+Fix any issues before proceeding.
+
+### 5. Push Branch
+
+```bash
+git push -u origin $(git branch --show-current)
+```
+
+### 6. Create Pull Request
+
+#### PR Title
+```
+{ticket-id}: {Ticket Summary}
+```
+
+#### PR Description
+
+Use this template:
+
+```markdown
+## Summary
+Brief description of what this PR accomplishes.
+
+## Jira Ticket
+[{ticket-id}](https://your-org.atlassian.net/browse/{ticket-id})
+
+## Changes Made
+- Change 1: Description
+- Change 2: Description
+- Change 3: Description
+
+## Type of Change
+- [ ] 🐛 Bug fix
+- [ ] ✨ New feature
+- [ ] 💥 Breaking change
+- [ ] 📝 Documentation
+- [ ] 🔧 Refactoring
+
+## Testing
+- [ ] Unit tests added/updated
+- [ ] Manual testing performed
+- Describe test cases here
+
+## Screenshots
+(If UI changes, add before/after screenshots)
+
+## Checklist
+- [ ] Code follows project style guidelines
+- [ ] Self-review completed
+- [ ] Documentation updated
+- [ ] Tests pass locally
+```
+
+#### PR Settings
+- **Source**: Current branch
+- **Target**: `<base-branch>` resolved from `.agents-toolkit.json` (fallback: `main`)
+- **Reviewers**: Based on changed files
+
+### 7. Link PR to Jira
+
+Add comment to Jira ticket:
+```markdown
+## Pull Request Created
+- PR: [PR Title](PR_URL)
+- Target: `<base-branch>` branch
+- Reviewers: @assigned-reviewers
+
+## Changes
+- Summary of changes made
+```
+
+## Output
+
+Report:
+1. ✅ PR URL
+2. ✅ Jira ticket linked
+3. ✅ Reviewers assigned
+
+## Next Steps
+- Wait for review
+- Address feedback
+- Use `finalize-pr` after approval

package/templates/shared/prompts/finalize-pr.prompt.md

@@ -0,0 +1,150 @@
+---
+agent: agent
+description: Finalize a pull request after approval and prepare for merge
+---
+
+# Finalize Pull Request
+
+Finalize PR for Jira ticket **{ticket-id}** after approval and prepare for merge.
+
+## Prerequisites
+- PR has been approved
+- Reference: `.github/prompts/_partials/git-operations.md`
+- Reference: `.github/prompts/_partials/validations.md`
+- Reference: `.github/prompts/_partials/jira-integration.md`
+
+## Steps
+
+### 1. Verify PR Status
+
+Check:
+- All required approvals in place
+- CI/CD pipeline passed
+- No unresolved review comments
+
+### 2. Address Review Comments
+
+If there are unresolved comments:
+- List each comment
+- Address feedback
+- Push additional commits if needed
+- Request re-review if changes are significant
+
+### 3. Sync with Base Branch
+
+```bash
+BASE_BRANCH=$(node -e "try{const c=require('./.agents-toolkit.json');console.log(c.pr?.targetBranch||c.git?.defaultBranch||'main')}catch{console.log('main')}")
+git fetch origin
+git rebase "origin/${BASE_BRANCH}"
+```
+
+If conflicts:
+1. Resolve each conflict
+2. Stage resolved files: `git add <file>`
+3. Continue rebase: `git rebase --continue`
+
+Push updated branch:
+```bash
+git push --force-with-lease
+```
+
+### 4. Final Validations
+
+Run complete validation suite:
+```bash
+npm run lint --if-present
+npm run type-check --if-present
+if [ -f tsconfig.json ]; then npx tsc --noEmit; fi
+npm run test --if-present
+npm run build --if-present
+```
+
+Verify:
+- No regressions after rebase
+- All tests still pass
+- No new warnings
+
+### 5. Update Jira Ticket
+
+Add comment:
+```markdown
+## Ready for Merge
+- All approvals received
+- CI/CD passed
+- Branch synced with `<base-branch>`
+- Tests passing
+
+## Merge Notes
+- Merge strategy: Squash recommended
+- Post-merge: Deploy to staging for QA
+```
+
+Transition ticket to appropriate status:
+- "In Review" → "Ready for QA" or
+- "In Review" → "Done" (if no QA needed)
+
+### 6. Clean Up
+
+- [ ] Delete temporary planning docs from `docs/` (if applicable)
+- [ ] Ensure final documentation is complete
+- [ ] Verify commit history is clean
+
+### 7. Prepare Merge
+
+**Recommended merge strategy**: Squash merge
+
+**Final commit message format**:
+```
+{ticket-id}: {Summary of changes}
+
+- Key change 1
+- Key change 2
+- Key change 3
+```
+
+### 8. Post-Merge Tasks
+
+After merge is complete:
+
+```bash
+# Delete local branch
+git checkout "$BASE_BRANCH"
+git pull origin "$BASE_BRANCH"
+git branch -d <branch-name>
+
+# Delete remote branch (if not auto-deleted)
+git push origin --delete <branch-name>
+
+# Clean up stale references
+git remote prune origin
+```
+
+Update Jira:
+- Transition to "Done" or "Ready for QA"
+- Add deployment comment if applicable
+
+## Output
+
+### Completion Report
+
+✅ **Pre-Merge Checklist**
+- [ ] All approvals received
+- [ ] CI/CD passed
+- [ ] Branch synced with base branch
+- [ ] Final validations passed
+- [ ] Documentation complete
+
+✅ **Merge Ready**
+- Commit message prepared
+- Merge strategy confirmed
+
+✅ **Post-Merge Tasks**
+- [ ] Local branch deleted
+- [ ] Remote branch deleted
+- [ ] Jira ticket updated
+- [ ] Team notified (if needed)
+
+## Notes
+- If merge conflicts arise during squash, resolve and complete
+- Notify team if deployment is needed
+- Update related documentation if this was a major feature

package/templates/shared/prompts/fix-issues.prompt.md

@@ -0,0 +1,92 @@
+---
+agent: agent
+description: Fix failing tests and lint errors
+---
+
+# Fix Code Issues
+
+Fix failing tests, lint errors, and type errors in the codebase.
+
+## Steps
+
+### 1. Run All Checks
+
+```bash
+npm run lint --if-present 2>&1 | head -100
+npm run type-check --if-present 2>&1 | head -100
+if [ -f tsconfig.json ]; then npx tsc --noEmit 2>&1 | head -100; fi
+npm run test --if-present 2>&1 | head -100
+```
+
+### 2. Categorize Issues
+
+Sort issues by type:
+- **Lint errors**: ESLint violations
+- **Type errors**: TypeScript compilation errors
+- **Test failures**: Failed unit tests
+
+### 3. Fix Lint Errors
+
+#### Auto-fixable
+```bash
+npm run lint --if-present -- --fix
+```
+
+#### Manual fixes
+For each remaining lint error:
+1. Read the error message
+2. Locate the file and line
+3. Apply the appropriate fix
+4. Verify fix resolved the issue
+
+### 4. Fix Type Errors
+
+For each type error:
+1. Read the TypeScript error message
+2. Understand the type mismatch
+3. Apply fix:
+   - Add missing type
+   - Fix type assertion
+   - Update interface
+   - Handle null/undefined
+
+### 5. Fix Test Failures
+
+For each failing test:
+1. Read the test output
+2. Understand what's expected vs actual
+3. Determine if issue is:
+   - **Test is wrong**: Update test
+   - **Code is wrong**: Fix implementation
+   - **Missing mock**: Add mock data
+
+### 6. Verify All Fixed
+
+```bash
+npm run lint --if-present
+npm run type-check --if-present
+if [ -f tsconfig.json ]; then npx tsc --noEmit; fi
+npm run test --if-present
+npm run build --if-present
+```
+
+## Output
+
+### Fixed Issues
+
+| Type | Count | Files |
+|------|-------|-------|
+| Lint | N | file1, file2 |
+| Types | N | file3, file4 |
+| Tests | N | test1, test2 |
+
+### Remaining Issues
+List any issues that couldn't be auto-fixed.
+
+### Changes Made
+Summary of fixes applied.
+
+## Notes
+- Always commit after fixing each category
+- Run full validation after all fixes
+- Some issues may require architectural changes

package/templates/shared/prompts/new-wp-component.prompt.md

@@ -0,0 +1,51 @@
+---
+description: Scaffold a new component (Service, Controller, View, Model, Repository) in a Silver Assist WordPress plugin
+agent: agent
+tools:
+  - run_in_terminal
+  - read_file
+  - replace_string_in_file
+  - create_file
+---
+
+# New Component
+
+Scaffold a new component in the current Silver Assist plugin following the LoadableInterface architecture.
+
+## Inputs
+
+Ask the user:
+1. **Component type** — Service, Controller, View, Model, or Repository?
+2. **Component name** — e.g., `EmailNotification`, `ReportGenerator`
+3. **Category/subdirectory** — e.g., `Admin`, `Frontend`, `Email` (optional)
+
+## Steps
+
+1. **Detect plugin** — Find the plugin root, namespace, and existing component structure.
+
+2. **Create the component file** — Use the create-component skill templates to generate the class file in the appropriate directory:
+   - `includes/Service/` for Services (LoadableInterface, priority 20)
+   - `includes/Controller/Admin/` or `includes/Controller/Frontend/` for Controllers (LoadableInterface, priority 30)
+   - `includes/View/Admin/` or `includes/View/Frontend/` for Views (static class, no LoadableInterface)
+   - `includes/Model/` for Models (plain object, no LoadableInterface)
+   - `includes/Repository/` for Repositories (no LoadableInterface, used by Services)
+
+3. **Register in Plugin.php** — If the component implements LoadableInterface, add it to the `$components` array in `Plugin.php` with the correct priority.
+
+4. **Create test file** — Generate a corresponding test file at `tests/` following the testing conventions:
+   - Test class extends the plugin's base `TestCase` (which extends `WP_UnitTestCase`)
+   - Use `camelCase` for test methods, `snake_case` for lifecycle methods
+   - Include `@group` and `@coversDefaultClass` PHPDoc annotations
+
+5. **Verify** — Run PHPCS and PHPStan on the new file:
+   ```bash
+   vendor/bin/phpcs path/to/NewFile.php
+   vendor/bin/phpstan analyse path/to/NewFile.php --memory-limit=1G
+   ```
+
+## Important
+
+- The create-component skill has full templates and MVC flow documentation — use it.
+- Views must NEVER instantiate Services directly. Controllers coordinate Service → View.
+- All public methods must have `@param` and `@return` PHPDoc with concrete types (PHPStan level 8).
+- Use the plugin's text domain for all translatable strings.

package/templates/shared/prompts/new-wp-plugin.prompt.md

@@ -0,0 +1,46 @@
+---
+description: Create a new Silver Assist WordPress plugin from scratch with full architecture and CI/CD
+agent: agent
+tools:
+  - run_in_terminal
+  - read_file
+  - replace_string_in_file
+  - create_file
+---
+
+# New Plugin
+
+Scaffold a new Silver Assist WordPress plugin with the standard architecture, quality tools, and CI/CD pipeline.
+
+## Inputs
+
+Ask the user:
+1. **Plugin name** — Human-readable name (e.g., "Silver Assist Cache Manager")
+2. **Plugin slug** — Kebab-case slug (e.g., `silver-assist-cache-manager`)
+3. **Brief description** — One-line description of the plugin's purpose
+4. **Minimum PHP version** — Default: 8.2
+
+## Steps
+
+Follow the plugin-creation skill instructions completely. The skill has the full file structure, templates, and configuration for:
+
+1. **Core files** — Main plugin file, `Plugin.php` with singleton + LoadableInterface loader, `Activator.php`
+2. **Composer setup** — `composer.json` with PSR-4 autoloading, dev dependencies (PHPCS, PHPStan, PHPUnit)
+3. **Quality configs** — `phpcs.xml`, `phpstan.neon`, `phpunit.xml.dist`
+4. **CI/CD** — GitHub Actions workflows for quality checks and releases
+5. **Scripts** — `build-release.sh`, `run-quality-checks.sh`, `update-version.sh`
+6. **Tests** — Bootstrap, base `TestCase`, first sample test
+7. **Documentation** — `README.md`, `CHANGELOG.md`, `.github/copilot-instructions.md`
+8. **Git setup** — `.gitignore`, initial commit
+
+After scaffolding, run quality checks to verify everything works:
+```bash
+composer install
+./scripts/run-quality-checks.sh --skip-wp-setup phpcs phpstan
+```
+
+## Important
+
+- Use the plugin-creation skill — it has the complete canonical templates.
+- The `.github/copilot-instructions.md` should contain ONLY plugin-specific context (namespace, text domain, key features). Global standards are handled by `~/.copilot/instructions/`.
+- Pin all GitHub Actions to SHA hashes, not version tags.