@syntesseraai/opencode-feature-factory 0.2.1 → 0.2.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -204,12 +204,12 @@ Use ff-severity-classification when making changes:
204
204
 
205
205
  ## Workflow
206
206
 
207
- 1. Load required skills (mini-plan, todo-management, severity-classification)
207
+ 1. Load required skills (ff-mini-plan, ff-todo-management, ff-severity-classification)
208
208
  2. Load or create implementation plan
209
209
  3. Create todo list for execution
210
210
  4. Execute implementation steps
211
211
  5. Run quality checks (lint, typecheck, tests)
212
- 6. Self-assess changes using severity-classification
212
+ 6. Self-assess changes using ff-severity-classification
213
213
  7. Invoke @reviewing agent for validation
214
214
  8. Address findings, create new todos as needed
215
215
  9. Iterate until validation passes or only low-priority issues remain
@@ -169,12 +169,12 @@ Use ff-severity-classification skill standards:
169
169
 
170
170
  ## Workflow
171
171
 
172
- 1. Load required skills (mini-plan, todo-management, severity-classification, report-templates)
173
- 2. Create mini-plan for validation approach
172
+ 1. Load required skills (ff-mini-plan, ff-todo-management, ff-severity-classification, ff-report-templates)
173
+ 2. Create ff-mini-plan for validation approach
174
174
  3. Create todo list from the plan
175
175
  4. Execute validation steps, updating todos in real-time
176
- 5. Use severity-classification to categorize findings
177
- 6. Format output using report-templates
176
+ 5. Use ff-severity-classification to categorize findings
177
+ 6. Format output using ff-report-templates
178
178
  7. Mark all todos complete before finishing
179
179
 
180
180
  Remember: Your role is to be the "gatekeeper" ensuring requirements are fully and correctly implemented before proceeding.
@@ -173,11 +173,11 @@ Use ff-severity-classification skill standards:
173
173
 
174
174
  ## Workflow
175
175
 
176
- 1. Load required skills (mini-plan, todo-management, severity-classification, report-templates)
177
- 2. Create mini-plan for review approach
176
+ 1. Load required skills (ff-mini-plan, ff-todo-management, ff-severity-classification, ff-report-templates)
177
+ 2. Create ff-mini-plan for review approach
178
178
  3. Create todo list from the plan
179
179
  4. Execute review steps, updating todos in real-time
180
- 5. Identify issues and classify using severity-classification
181
- 6. Format output using report-templates (Code Review template)
180
+ 5. Identify issues and classify using ff-severity-classification
181
+ 6. Format output using ff-report-templates (Code Review template)
182
182
  7. Mark all todos complete before finishing
183
183
  8. Recommend delegating to other agents if specialized issues found
@@ -208,11 +208,11 @@ Use ff-severity-classification skill standards with security-specific definition
208
208
 
209
209
  ## Workflow
210
210
 
211
- 1. Load required skills (mini-plan, todo-management, severity-classification, report-templates)
212
- 2. Create mini-plan for audit approach
211
+ 1. Load required skills (ff-mini-plan, ff-todo-management, ff-severity-classification, ff-report-templates)
212
+ 2. Create ff-mini-plan for audit approach
213
213
  3. Create todo list from the plan
214
214
  4. Execute security checklist, updating todos in real-time
215
- 5. Identify vulnerabilities and classify using severity-classification
216
- 6. Format output using report-templates (Security Audit template)
215
+ 5. Identify vulnerabilities and classify using ff-severity-classification
216
+ 6. Format output using ff-report-templates (Security Audit template)
217
217
  7. Mark all todos complete before finishing
218
218
  8. Recommend delegating to other agents if additional issues found
@@ -191,13 +191,13 @@ When multiple agents report findings:
191
191
  ## Workflow
192
192
 
193
193
  1. Load required skills
194
- 2. Create mini-plan for orchestration
194
+ 2. Create ff-mini-plan for orchestration
195
195
  3. Create todo list for tracking agent launches
196
196
  4. Launch all 4 agents in parallel using Task tool
197
197
  5. As results arrive, update todos and aggregate findings
198
198
  6. Apply severity classification to all issues
199
199
  7. Calculate verdict based on approval criteria
200
- 8. Format comprehensive report using report-templates
200
+ 8. Format comprehensive report using ff-report-templates
201
201
  9. Mark all todos complete
202
202
  10. Present final validation report
203
203
 
@@ -169,12 +169,12 @@ Use ff-severity-classification skill standards:
169
169
 
170
170
  ## Workflow
171
171
 
172
- 1. Load required skills (mini-plan, todo-management, severity-classification, report-templates)
173
- 2. Create mini-plan for reviewing all 6 pillars
172
+ 1. Load required skills (ff-mini-plan, ff-todo-management, ff-severity-classification, ff-report-templates)
173
+ 2. Create ff-mini-plan for reviewing all 6 pillars
174
174
  3. Create todo list from the plan (one todo per pillar)
175
175
  4. Review each pillar, updating todos in real-time
176
176
  5. Score each pillar and identify issues
177
- 6. Format output using report-templates (Well-Architected template)
177
+ 6. Format output using ff-report-templates (Well-Architected template)
178
178
  7. Mark all todos complete before finishing
179
179
  8. Invoke other agents if specialized issues found
180
180
 
@@ -157,13 +157,13 @@ Recommend escalation to full architectural planning when:
157
157
 
158
158
  ## Workflow
159
159
 
160
- 1. Load required skills (mini-plan, todo-management, report-templates)
160
+ 1. Load required skills (ff-mini-plan, ff-todo-management, ff-report-templates)
161
161
  2. Create todo list for planning process
162
162
  3. Analyze requirements and mark todo complete
163
163
  4. Assess complexity and mark todo complete
164
164
  5. Identify files and mark todo complete
165
165
  6. Create implementation plan
166
- 7. Format output using report-templates
166
+ 7. Format output using ff-report-templates
167
167
  8. Mark all todos complete
168
168
  9. Hand off plan to @building agent for implementation
169
169
 
@@ -19,7 +19,7 @@ You are a research specialist for Feature Factory. Your role is to investigate e
19
19
  At the start of EVERY research task:
20
20
 
21
21
  1. **Check current date** using bash `date` command
22
- 2. **Load the research-methods skill** for research methodology
22
+ 2. **Load the ff-research-methods skill** for research methodology
23
23
  3. **Load the ff-mini-plan skill** and create a research plan
24
24
  4. **Load the ff-todo-management skill** and create a todo list
25
25
  5. **Load the ff-report-templates skill** for output formatting
@@ -68,7 +68,7 @@ Use ff-mini-plan skill:
68
68
 
69
69
  ### Step 3: Execute Research
70
70
 
71
- Follow the research hierarchy from research-methods skill:
71
+ Follow the research hierarchy from ff-research-methods skill:
72
72
 
73
73
  1. **Web Search** (search_web) - Find current best practices and documentation
74
74
  2. **Read URLs** (read_url) - Extract detailed information from specific pages
@@ -279,7 +279,7 @@ Structure research findings using ff-report-templates:
279
279
  ## Workflow
280
280
 
281
281
  1. **Start:** Check current date with bash `date`
282
- 2. **Plan:** Load research-methods, ff-mini-plan skills and create research plan
282
+ 2. **Plan:** Load ff-research-methods, ff-mini-plan skills and create research plan
283
283
  3. **Track:** Load ff-todo-management and create todo list
284
284
  4. **Research:** Execute research using MCP tools following hierarchy
285
285
  5. **Synthesize:** Consolidate findings using ff-report-templates
@@ -292,7 +292,7 @@ Structure research findings using ff-report-templates:
292
292
 
293
293
  ```
294
294
  1. bash: date → Sun Feb 1 18:25:00 UTC 2026
295
- 2. Load skills: research-methods, mini-plan, todo-management, report-templates
295
+ 2. Load skills: ff-research-methods, ff-mini-plan, ff-todo-management, ff-report-templates
296
296
  3. Create plan: Research RSC concepts, docs, examples, patterns
297
297
  4. Create todos and track:
298
298
  - [x] Check date
@@ -304,7 +304,7 @@ Structure research findings using ff-report-templates:
304
304
  - read_url: "https://react.dev/reference/react/use-server"
305
305
  - codesearch: "React Server Components examples"
306
306
  - gh_grep: "'use server'", language: TypeScript
307
- 6. Format findings with report-templates
307
+ 6. Format findings with ff-report-templates
308
308
  7. Return structured report to invoking agent
309
309
  ```
310
310
 
@@ -213,7 +213,7 @@ When combining results from multiple agents:
213
213
 
214
214
  ## Workflow
215
215
 
216
- 1. Load required skills (todo-management, report-templates, severity-classification)
216
+ 1. Load required skills (ff-todo-management, ff-report-templates, ff-severity-classification)
217
217
  2. Create review todo list
218
218
  3. Mark "Launch validation" as in_progress
219
219
  4. Invoke @ff-validate agent
package/bin/ff-deploy.js CHANGED
@@ -33,7 +33,7 @@ const DEFAULT_MCP_CONFIG = {
33
33
  type: 'remote',
34
34
  url: 'https://mcp.jina.ai/v1',
35
35
  headers: {
36
- Authorization: 'Bearer jina_5a6cb847e5d44f738658c722c0c25c8bqjnj_wxVri8AuP-3awHMf1Zh6Xi7',
36
+ Authorization: 'Bearer {env:JINAAI_API_KEY}',
37
37
  },
38
38
  },
39
39
  gh_grep: {
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "$schema": "https://json.schemastore.org/package.json",
3
3
  "name": "@syntesseraai/opencode-feature-factory",
4
- "version": "0.2.1",
4
+ "version": "0.2.3",
5
5
  "description": "OpenCode plugin for Feature Factory agents - provides sub-agents and skills for validation, review, security, and architecture assessment",
6
6
  "type": "module",
7
7
  "license": "MIT",
@@ -1,5 +1,5 @@
1
1
  ---
2
- name: research-methods
2
+ name: ff-research-methods
3
3
  description: Research methodology for investigating external topics using MCP tools. Use this skill to search for current information, best practices, and implementation examples.
4
4
  license: MIT
5
5
  compatibility: opencode
package/src/index.ts CHANGED
@@ -17,15 +17,6 @@ export const AGENT_PATHS = {
17
17
  'ff-validate': './agents/ff-validate.md',
18
18
  };
19
19
 
20
- // Backward compatibility: Export tool plugins that delegate to sub-agents
21
- // These tools now invoke the corresponding sub-agents instead of returning prompts
22
- export { FFAcceptancePlugin } from './tools/ffAcceptance';
23
- export { FFMiniPlanPlugin } from './tools/ffMiniPlan';
24
- export { FFReviewPlugin } from './tools/ffReview';
25
- export { FFSecurityPlugin } from './tools/ffSecurity';
26
- export { FFValidatePlugin } from './tools/ffValidate';
27
- export { FFWellArchitectedPlugin } from './tools/ffWellArchitected';
28
-
29
20
  const SERVICE_NAME = 'feature-factory';
30
21
 
31
22
  type Client = PluginInput['client'];
@@ -1,31 +0,0 @@
1
- import { type Plugin, tool } from '@opencode-ai/plugin';
2
-
3
- /**
4
- * @ff-acceptance Tool Plugin (Backward Compatibility)
5
- *
6
- * This tool delegates to the @ff-acceptance sub-agent.
7
- *
8
- * NOTE: New code should use the sub-agent directly via @ff-acceptance
9
- * or invoke it through the @ff-validate orchestrator.
10
- */
11
-
12
- export const FFAcceptancePlugin: Plugin = async (_ctx) => {
13
- return {
14
- tool: {
15
- ff_acceptance: tool({
16
- description:
17
- 'Validates implementation against acceptance criteria (@ff-acceptance), checks if code meets all requirements. DEPRECATED: Use @ff-acceptance sub-agent directly.',
18
- args: {
19
- task: tool.schema
20
- .string()
21
- .describe('The validation task or acceptance criteria to check'),
22
- },
23
- async execute({ task }) {
24
- // Invoke the sub-agent via the Task tool
25
- // This maintains backward compatibility while using the new sub-agent
26
- return `Invoking @ff-acceptance sub-agent to validate: ${task}\n\nPlease wait for the acceptance validation to complete. The @ff-acceptance agent will:\n1. Create a validation plan\n2. Check all acceptance criteria\n3. Provide a detailed report with findings\n\nFor direct access to the sub-agent, use: @ff-acceptance ${task}`;
27
- },
28
- }),
29
- },
30
- };
31
- };
@@ -1,28 +0,0 @@
1
- import { type Plugin, tool } from '@opencode-ai/plugin';
2
-
3
- /**
4
- * @ff-mini-plan Tool Plugin (Backward Compatibility)
5
- *
6
- * This tool loads the ff-mini-plan skill and provides guidance.
7
- *
8
- * NOTE: New code should use the skill directly via the skill tool
9
- * or invoke it through sub-agents that load it automatically.
10
- */
11
-
12
- export const FFMiniPlanPlugin: Plugin = async (ctx) => {
13
- return {
14
- tool: {
15
- ff_mini_plan: tool({
16
- description:
17
- 'Creates mini implementation plans for smaller tasks (2-5 steps) (@ff-mini-plan), quick planning, small fixes. DEPRECATED: Load the ff-mini-plan skill directly.',
18
- args: {
19
- task: tool.schema.string().describe('The simple task or issue description to plan for'),
20
- },
21
- async execute({ task }) {
22
- // Provide guidance on using the skill instead
23
- return `# Mini Planning\n\nFor task: ${task}\n\n## Using the ff-mini-plan Skill\n\nThe ff-mini-plan skill is now available globally. To use it:\n\n1. **In sub-agents**: Skills are loaded automatically at the start of tasks\n2. **Manually**: Use the skill tool to load ff-mini-plan\n\n## Quick Planning Guide\n\nThe mini-plan skill helps create 2-5 step plans for simple tasks:\n\n### Planning Process:\n1. Assess task complexity (suitable for 2-5 steps?)\n2. Create concrete steps with specific files\n3. Estimate effort and complexity\n4. Identify quick wins\n\n### Escalation Criteria:\n- Requires more than 5 implementation steps\n- Affects multiple components or services\n- Requires architecture decisions\n- Has security implications\n\n### Example Plan Structure:\n\`\`\`\n# Mini Plan: [Task]\n\n**Status:** Ready\n**Time Estimate:** 5-10 minutes\n**Complexity:** Simple\n\n## 📋 Steps\n\n1. **[Step 1]**\n - What to do: [Action]\n - Files: \`file.ts\`\n - Tests: [Verification]\n\n2. **[Step 2]**\n - What to do: [Action]\n - Files: \`file.ts\`\n - Tests: [Verification]\n\n## ⚡ Quick Wins\n\n- [Improvement] - [Benefit]\n\`\`\`\n\nFor comprehensive planning, use @ff-validate to run all validation agents with mini-plans.`;
24
- },
25
- }),
26
- },
27
- };
28
- };
@@ -1,28 +0,0 @@
1
- import { type Plugin, tool } from '@opencode-ai/plugin';
2
-
3
- /**
4
- * @ff-review Tool Plugin (Backward Compatibility)
5
- *
6
- * This tool delegates to the @ff-review sub-agent.
7
- *
8
- * NOTE: New code should use the sub-agent directly via @ff-review
9
- * or invoke it through the @ff-validate orchestrator.
10
- */
11
-
12
- export const FFReviewPlugin: Plugin = async (_ctx) => {
13
- return {
14
- tool: {
15
- ff_review: tool({
16
- description:
17
- 'Reviews code changes for correctness, quality, and test coverage (@ff-review), code review, quality check. DEPRECATED: Use @ff-review sub-agent directly.',
18
- args: {
19
- task: tool.schema.string().describe('The code review task or diff to analyze'),
20
- },
21
- async execute({ task }) {
22
- // Invoke the sub-agent via the Task tool
23
- return `Invoking @ff-review sub-agent to review: ${task}\n\nPlease wait for the code review to complete. The @ff-review agent will:\n1. Create a review plan\n2. Check correctness, quality, and tests\n3. Provide a detailed report with findings\n\nFor direct access to the sub-agent, use: @ff-review ${task}`;
24
- },
25
- }),
26
- },
27
- };
28
- };
@@ -1,28 +0,0 @@
1
- import { type Plugin, tool } from '@opencode-ai/plugin';
2
-
3
- /**
4
- * @ff-security Tool Plugin (Backward Compatibility)
5
- *
6
- * This tool delegates to the @ff-security sub-agent.
7
- *
8
- * NOTE: New code should use the sub-agent directly via @ff-security
9
- * or invoke it through the @ff-validate orchestrator.
10
- */
11
-
12
- export const FFSecurityPlugin: Plugin = async (_ctx) => {
13
- return {
14
- tool: {
15
- ff_security: tool({
16
- description:
17
- 'Performs deep security audits on code changes (@ff-security), security check, vulnerability audit. DEPRECATED: Use @ff-security sub-agent directly.',
18
- args: {
19
- task: tool.schema.string().describe('The security audit task or code to analyze'),
20
- },
21
- async execute({ task }) {
22
- // Invoke the sub-agent via the Task tool
23
- return `Invoking @ff-security sub-agent to audit: ${task}\n\nPlease wait for the security audit to complete. The @ff-security agent will:\n1. Create an audit plan\n2. Check for OWASP Top 10 and other vulnerabilities\n3. Provide a detailed security report\n\nFor direct access to the sub-agent, use: @ff-security ${task}`;
24
- },
25
- }),
26
- },
27
- };
28
- };
@@ -1,28 +0,0 @@
1
- import { type Plugin, tool } from '@opencode-ai/plugin';
2
-
3
- /**
4
- * @ff-validate Tool Plugin (Backward Compatibility)
5
- *
6
- * This tool delegates to the @ff-validate sub-agent.
7
- *
8
- * NOTE: New code should use the sub-agent directly via @ff-validate
9
- * for comprehensive validation.
10
- */
11
-
12
- export const FFValidatePlugin: Plugin = async (_ctx) => {
13
- return {
14
- tool: {
15
- ff_validate: tool({
16
- description:
17
- 'Orchestrates comprehensive validation by running multiple review agents in parallel (@ff-validate), validate changes, comprehensive review. DEPRECATED: Use @ff-validate sub-agent directly.',
18
- args: {
19
- task: tool.schema.string().describe('The validation task description'),
20
- },
21
- async execute({ task }) {
22
- // Invoke the sub-agent via the Task tool
23
- return `Invoking @ff-validate sub-agent to orchestrate comprehensive validation: ${task}\n\nPlease wait for the validation to complete. The @ff-validate agent will:\n1. Create an orchestration plan\n2. Run all validation agents in parallel:\n - @ff-acceptance (requirements validation)\n - @ff-review (code quality)\n - @ff-security (security audit)\n - @ff-well-architected (architecture review)\n3. Aggregate results and provide a comprehensive report\n\nFor direct access to the orchestrator, use: @ff-validate ${task}`;
24
- },
25
- }),
26
- },
27
- };
28
- };
@@ -1,30 +0,0 @@
1
- import { type Plugin, tool } from '@opencode-ai/plugin';
2
-
3
- /**
4
- * @ff-well-architected Tool Plugin (Backward Compatibility)
5
- *
6
- * This tool delegates to the @ff-well-architected sub-agent.
7
- *
8
- * NOTE: New code should use the sub-agent directly via @ff-well-architected
9
- * or invoke it through the @ff-validate orchestrator.
10
- */
11
-
12
- export const FFWellArchitectedPlugin: Plugin = async (_ctx) => {
13
- return {
14
- tool: {
15
- ff_well_architected: tool({
16
- description:
17
- 'Reviews code against AWS Well-Architected Framework pillars (@ff-well-architected), architecture review, AWS best practices. DEPRECATED: Use @ff-well-architected sub-agent directly.',
18
- args: {
19
- task: tool.schema
20
- .string()
21
- .describe('The architecture review task or system design to analyze'),
22
- },
23
- async execute({ task }) {
24
- // Invoke the sub-agent via the Task tool
25
- return `Invoking @ff-well-architected sub-agent to review: ${task}\n\nPlease wait for the architecture review to complete. The @ff-well-architected agent will:\n1. Create a review plan\n2. Assess against AWS Well-Architected 6 pillars:\n - Operational Excellence\n - Security\n - Reliability\n - Performance Efficiency\n - Cost Optimization\n - Sustainability\n3. Provide a detailed report with pillar scores\n\nFor direct access to the sub-agent, use: @ff-well-architected ${task}`;
26
- },
27
- }),
28
- },
29
- };
30
- };