mirror of
https://github.com/AutoMaker-Org/automaker.git
synced 2026-01-30 06:12:03 +00:00
788 lines
34 KiB
JavaScript
788 lines
34 KiB
JavaScript
const contextManager = require("./context-manager");
|
|
|
|
/**
|
|
* Prompt Builder - Generates prompts for different agent tasks
|
|
*/
|
|
class PromptBuilder {
|
|
/**
|
|
* Build the prompt for implementing a specific feature
|
|
*/
|
|
async buildFeaturePrompt(feature, projectPath) {
|
|
const skipTestsNote = feature.skipTests
|
|
? `\n**⚠️ IMPORTANT - Manual Testing Mode:**\nThis feature has skipTests=true, which means:\n- DO NOT commit changes automatically\n- DO NOT mark as verified - it will automatically go to "waiting_approval" status\n- The user will manually review and commit the changes\n- Just implement the feature and mark it as verified (it will be converted to waiting_approval)\n`
|
|
: "";
|
|
|
|
let imagesNote = "";
|
|
if (feature.imagePaths && feature.imagePaths.length > 0) {
|
|
const imagesList = feature.imagePaths
|
|
.map(
|
|
(img, idx) =>
|
|
` ${idx + 1}. ${img.filename} (${img.mimeType})\n Path: ${
|
|
img.path
|
|
}`
|
|
)
|
|
.join("\n");
|
|
|
|
imagesNote = `\n**📎 Context Images Attached:**\nThe user has attached ${feature.imagePaths.length} image(s) for context. These images are provided both visually (in the initial message) and as files you can read:
|
|
|
|
${imagesList}
|
|
|
|
You can use the Read tool to view these images at any time during implementation. Review them carefully before implementing.\n`;
|
|
}
|
|
|
|
// Get context files preview
|
|
const contextFilesPreview = await contextManager.getContextFilesPreview(
|
|
projectPath
|
|
);
|
|
|
|
// Get memory content (lessons learned from previous runs)
|
|
const memoryContent = await contextManager.getMemoryContent(projectPath);
|
|
|
|
// Build mode header for this feature
|
|
const modeHeader = feature.skipTests
|
|
? `**🔨 MODE: Manual Review (No Automated Tests)**
|
|
This feature is set for manual review - focus on clean implementation without automated tests.`
|
|
: `**🧪 MODE: Test-Driven Development (TDD)**
|
|
This feature requires automated Playwright tests to verify the implementation.`;
|
|
|
|
return `You are working on a feature implementation task.
|
|
|
|
${modeHeader}
|
|
${memoryContent}
|
|
**Current Feature to Implement:**
|
|
|
|
ID: ${feature.id}
|
|
Category: ${feature.category || "Uncategorized"}
|
|
Description: ${feature.description || feature.summary || feature.title || "No description provided"}
|
|
${skipTestsNote}${imagesNote}${contextFilesPreview}
|
|
**Steps to Complete:**
|
|
${(feature.steps || []).map((step, i) => `${i + 1}. ${step}`).join("\n") || "No specific steps provided - implement based on description"}
|
|
|
|
**Your Task:**
|
|
|
|
1. Read the project files to understand the current codebase structure
|
|
2. Implement the feature according to the description and steps
|
|
${
|
|
feature.skipTests
|
|
? "3. Test the implementation manually (no automated tests needed for skipTests features)"
|
|
: "3. Write Playwright tests to verify the feature works correctly\n4. Run the tests and ensure they pass\n5. **DELETE the test file(s) you created** - tests are only for immediate verification"
|
|
}
|
|
${
|
|
feature.skipTests ? "4" : "6"
|
|
}. **CRITICAL: Use the UpdateFeatureStatus tool to mark this feature as verified**
|
|
${
|
|
feature.skipTests
|
|
? "5. **DO NOT commit changes** - the user will review and commit manually"
|
|
: "7. Commit your changes with git"
|
|
}
|
|
|
|
**IMPORTANT - Updating Feature Status:**
|
|
|
|
When you have completed the feature${
|
|
feature.skipTests ? "" : " and all tests pass"
|
|
}, you MUST use the \`mcp__automaker-tools__UpdateFeatureStatus\` tool to update the feature status:
|
|
- Call the tool with: featureId="${feature.id}" and status="verified"
|
|
- **You can also include a summary parameter** to describe what was done: summary="Brief summary of changes"
|
|
- **DO NOT manually edit feature files** - this can cause race conditions
|
|
- The UpdateFeatureStatus tool safely updates the feature status without risk of corrupting other data
|
|
- **If skipTests=true, the tool will automatically convert "verified" to "waiting_approval"** - this is correct behavior
|
|
|
|
**IMPORTANT - Feature Summary (REQUIRED):**
|
|
|
|
When calling UpdateFeatureStatus, you MUST include a summary parameter that describes:
|
|
- What files were modified/created
|
|
- What functionality was added or changed
|
|
- Any notable implementation decisions
|
|
|
|
Example:
|
|
\`\`\`
|
|
UpdateFeatureStatus(featureId="${
|
|
feature.id
|
|
}", status="verified", summary="Added dark mode toggle to settings. Modified: settings.tsx, theme-provider.tsx. Created new useTheme hook.")
|
|
\`\`\`
|
|
|
|
The summary will be displayed on the Kanban card so the user can see what was done without checking the code.
|
|
|
|
**Important Guidelines:**
|
|
|
|
- Focus ONLY on implementing this specific feature
|
|
- Write clean, production-quality code
|
|
- Add proper error handling
|
|
${
|
|
feature.skipTests
|
|
? "- Skip automated testing (skipTests=true) - user will manually verify"
|
|
: "- Write comprehensive Playwright tests\n- Ensure all existing tests still pass\n- Mark the feature as passing only when all tests are green\n- **CRITICAL: Delete test files after verification** - tests accumulate and become brittle"
|
|
}
|
|
- **CRITICAL: Use UpdateFeatureStatus tool instead of editing feature files directly**
|
|
- **CRITICAL: Always include a summary when marking feature as verified**
|
|
${
|
|
feature.skipTests
|
|
? "- **DO NOT commit changes** - user will review and commit manually"
|
|
: "- Make a git commit when complete"
|
|
}
|
|
|
|
**Testing Utilities (CRITICAL):**
|
|
|
|
1. **Create/maintain tests/utils.ts** - Add helper functions for finding elements and common test operations
|
|
2. **Use utilities in tests** - Import and use helper functions instead of repeating selectors
|
|
3. **Add utilities as needed** - When you write a test, if you need a new helper, add it to utils.ts
|
|
4. **Update utilities when functionality changes** - If you modify components, update corresponding utilities
|
|
|
|
Example utilities to add:
|
|
- getByTestId(page, testId) - Find elements by data-testid
|
|
- getButtonByText(page, text) - Find buttons by text
|
|
- clickElement(page, testId) - Click an element by test ID
|
|
- fillForm(page, formData) - Fill form fields
|
|
- waitForElement(page, testId) - Wait for element to appear
|
|
|
|
This makes future tests easier to write and maintain!
|
|
|
|
**Test Deletion Policy:**
|
|
After tests pass, delete them immediately:
|
|
\`\`\`bash
|
|
rm tests/[feature-name].spec.ts
|
|
\`\`\`
|
|
|
|
Begin by reading the project structure and then implementing the feature.`;
|
|
}
|
|
|
|
/**
|
|
* Build the prompt for verifying a specific feature
|
|
*/
|
|
async buildVerificationPrompt(feature, projectPath) {
|
|
const skipTestsNote = feature.skipTests
|
|
? `\n**⚠️ IMPORTANT - Manual Testing Mode:**\nThis feature has skipTests=true, which means:\n- DO NOT commit changes automatically\n- DO NOT mark as verified - it will automatically go to "waiting_approval" status\n- The user will manually review and commit the changes\n- Just implement the feature and mark it as verified (it will be converted to waiting_approval)\n`
|
|
: "";
|
|
|
|
let imagesNote = "";
|
|
if (feature.imagePaths && feature.imagePaths.length > 0) {
|
|
const imagesList = feature.imagePaths
|
|
.map(
|
|
(img, idx) =>
|
|
` ${idx + 1}. ${img.filename} (${img.mimeType})\n Path: ${
|
|
img.path
|
|
}`
|
|
)
|
|
.join("\n");
|
|
|
|
imagesNote = `\n**📎 Context Images Attached:**\nThe user has attached ${feature.imagePaths.length} image(s) for context. These images are provided both visually (in the initial message) and as files you can read:
|
|
|
|
${imagesList}
|
|
|
|
You can use the Read tool to view these images at any time during implementation. Review them carefully before implementing.\n`;
|
|
}
|
|
|
|
// Get context files preview
|
|
const contextFilesPreview = await contextManager.getContextFilesPreview(
|
|
projectPath
|
|
);
|
|
|
|
// Get memory content (lessons learned from previous runs)
|
|
const memoryContent = await contextManager.getMemoryContent(projectPath);
|
|
|
|
// Build mode header for this feature
|
|
const modeHeader = feature.skipTests
|
|
? `**🔨 MODE: Manual Review (No Automated Tests)**
|
|
This feature is set for manual review - focus on completing implementation without automated tests.`
|
|
: `**🧪 MODE: Test-Driven Development (TDD)**
|
|
This feature requires automated Playwright tests to verify the implementation.`;
|
|
|
|
return `You are implementing and verifying a feature until it is complete and working correctly.
|
|
|
|
${modeHeader}
|
|
${memoryContent}
|
|
|
|
**Feature to Implement/Verify:**
|
|
|
|
ID: ${feature.id}
|
|
Category: ${feature.category || "Uncategorized"}
|
|
Description: ${feature.description || feature.summary || feature.title || "No description provided"}
|
|
Current Status: ${feature.status}
|
|
${skipTestsNote}${imagesNote}${contextFilesPreview}
|
|
**Steps that should be implemented:**
|
|
${(feature.steps || []).map((step, i) => `${i + 1}. ${step}`).join("\n") || "No specific steps provided - implement based on description"}
|
|
|
|
**Your Task:**
|
|
|
|
1. Read the project files to understand the current implementation
|
|
2. If the feature is not fully implemented, continue implementing it
|
|
${
|
|
feature.skipTests
|
|
? "3. Test the implementation manually (no automated tests needed for skipTests features)"
|
|
: `3. Write or update Playwright tests to verify the feature works correctly
|
|
4. Run the Playwright tests: npx playwright test tests/[feature-name].spec.ts
|
|
5. Check if all tests pass
|
|
6. **If ANY tests fail:**
|
|
- Analyze the test failures and error messages
|
|
- Fix the implementation code to make the tests pass
|
|
- Update test utilities in tests/utils.ts if needed
|
|
- Re-run the tests to verify the fixes
|
|
- **REPEAT this process until ALL tests pass**
|
|
7. **If ALL tests pass:**
|
|
- **DELETE the test file(s) for this feature** - tests are only for immediate verification`
|
|
}
|
|
${
|
|
feature.skipTests ? "4" : "8"
|
|
}. **CRITICAL: Use the UpdateFeatureStatus tool to mark this feature as verified**
|
|
${
|
|
feature.skipTests
|
|
? "5. **DO NOT commit changes** - the user will review and commit manually"
|
|
: "9. Explain what was implemented/fixed and that all tests passed\n10. Commit your changes with git"
|
|
}
|
|
|
|
**IMPORTANT - Updating Feature Status:**
|
|
|
|
When you have completed the feature${
|
|
feature.skipTests ? "" : " and all tests pass"
|
|
}, you MUST use the \`mcp__automaker-tools__UpdateFeatureStatus\` tool to update the feature status:
|
|
- Call the tool with: featureId="${feature.id}" and status="verified"
|
|
- **You can also include a summary parameter** to describe what was done: summary="Brief summary of changes"
|
|
- **DO NOT manually edit feature files** - this can cause race conditions
|
|
- The UpdateFeatureStatus tool safely updates the feature status without risk of corrupting other data
|
|
- **If skipTests=true, the tool will automatically convert "verified" to "waiting_approval"** - this is correct behavior
|
|
|
|
**IMPORTANT - Feature Summary (REQUIRED):**
|
|
|
|
When calling UpdateFeatureStatus, you MUST include a summary parameter that describes:
|
|
- What files were modified/created
|
|
- What functionality was added or changed
|
|
- Any notable implementation decisions
|
|
|
|
Example:
|
|
\`\`\`
|
|
UpdateFeatureStatus(featureId="${
|
|
feature.id
|
|
}", status="verified", summary="Added dark mode toggle to settings. Modified: settings.tsx, theme-provider.tsx. Created new useTheme hook.")
|
|
\`\`\`
|
|
|
|
The summary will be displayed on the Kanban card so the user can see what was done without checking the code.
|
|
|
|
**Testing Utilities:**
|
|
- Check if tests/utils.ts exists and is being used
|
|
- If utilities are outdated due to functionality changes, update them
|
|
- Add new utilities as needed for this feature's tests
|
|
- Ensure test utilities stay in sync with code changes
|
|
|
|
**Test Deletion Policy:**
|
|
After tests pass, delete them immediately:
|
|
\`\`\`bash
|
|
rm tests/[feature-name].spec.ts
|
|
\`\`\`
|
|
|
|
**Important:**
|
|
${
|
|
feature.skipTests
|
|
? "- Skip automated testing (skipTests=true) - user will manually verify\n- **DO NOT commit changes** - user will review and commit manually"
|
|
: "- **CONTINUE IMPLEMENTING until all tests pass** - don't stop at the first failure\n- Only mark as verified if Playwright tests pass\n- **CRITICAL: Delete test files after they pass** - tests should not accumulate\n- Update test utilities if functionality changed\n- Make a git commit when the feature is complete\n- Be thorough and persistent in fixing issues"
|
|
}
|
|
- **CRITICAL: Use UpdateFeatureStatus tool instead of editing feature files directly**
|
|
- **CRITICAL: Always include a summary when marking feature as verified**
|
|
|
|
Begin by reading the project structure and understanding what needs to be implemented or fixed.`;
|
|
}
|
|
|
|
/**
|
|
* Build prompt for resuming feature with previous context
|
|
*/
|
|
async buildResumePrompt(feature, previousContext, projectPath) {
|
|
const skipTestsNote = feature.skipTests
|
|
? `\n**⚠️ IMPORTANT - Manual Testing Mode:**\nThis feature has skipTests=true, which means:\n- DO NOT commit changes automatically\n- DO NOT mark as verified - it will automatically go to "waiting_approval" status\n- The user will manually review and commit the changes\n- Just implement the feature and mark it as verified (it will be converted to waiting_approval)\n`
|
|
: "";
|
|
|
|
// For resume, check both followUpImages and imagePaths
|
|
const imagePaths = feature.followUpImages || feature.imagePaths;
|
|
let imagesNote = "";
|
|
if (imagePaths && imagePaths.length > 0) {
|
|
const imagesList = imagePaths
|
|
.map((img, idx) => {
|
|
// Handle both FeatureImagePath objects and simple path strings
|
|
const path = typeof img === "string" ? img : img.path;
|
|
const filename =
|
|
typeof img === "string" ? path.split("/").pop() : img.filename;
|
|
const mimeType = typeof img === "string" ? "image/*" : img.mimeType;
|
|
return ` ${
|
|
idx + 1
|
|
}. ${filename} (${mimeType})\n Path: ${path}`;
|
|
})
|
|
.join("\n");
|
|
|
|
imagesNote = `\n**📎 Context Images Attached:**\nThe user has attached ${imagePaths.length} image(s) for context. These images are provided both visually (in the initial message) and as files you can read:
|
|
|
|
${imagesList}
|
|
|
|
You can use the Read tool to view these images at any time. Review them carefully.\n`;
|
|
}
|
|
|
|
// Get context files preview
|
|
const contextFilesPreview = await contextManager.getContextFilesPreview(
|
|
projectPath
|
|
);
|
|
|
|
// Get memory content (lessons learned from previous runs)
|
|
const memoryContent = await contextManager.getMemoryContent(projectPath);
|
|
|
|
// Build mode header for this feature
|
|
const modeHeader = feature.skipTests
|
|
? `**🔨 MODE: Manual Review (No Automated Tests)**
|
|
This feature is set for manual review - focus on clean implementation without automated tests.`
|
|
: `**🧪 MODE: Test-Driven Development (TDD)**
|
|
This feature requires automated Playwright tests to verify the implementation.`;
|
|
|
|
return `You are resuming work on a feature implementation that was previously started.
|
|
|
|
${modeHeader}
|
|
${memoryContent}
|
|
**Current Feature:**
|
|
|
|
ID: ${feature.id}
|
|
Category: ${feature.category || "Uncategorized"}
|
|
Description: ${feature.description || feature.summary || feature.title || "No description provided"}
|
|
${skipTestsNote}${imagesNote}${contextFilesPreview}
|
|
**Steps to Complete:**
|
|
${(feature.steps || []).map((step, i) => `${i + 1}. ${step}`).join("\n") || "No specific steps provided - implement based on description"}
|
|
|
|
**Previous Work Context:**
|
|
|
|
${previousContext || "No previous context available - this is a fresh start."}
|
|
|
|
**Your Task:**
|
|
|
|
Continue where you left off and complete the feature implementation:
|
|
|
|
1. Review the previous work context above to understand what has been done
|
|
2. Continue implementing the feature according to the description and steps
|
|
${
|
|
feature.skipTests
|
|
? "3. Test the implementation manually (no automated tests needed for skipTests features)"
|
|
: "3. Write Playwright tests to verify the feature works correctly (if not already done)\n4. Run the tests and ensure they pass\n5. **DELETE the test file(s) you created** - tests are only for immediate verification"
|
|
}
|
|
${
|
|
feature.skipTests ? "4" : "6"
|
|
}. **CRITICAL: Use the UpdateFeatureStatus tool to mark this feature as verified**
|
|
${
|
|
feature.skipTests
|
|
? "5. **DO NOT commit changes** - the user will review and commit manually"
|
|
: "7. Commit your changes with git"
|
|
}
|
|
|
|
**IMPORTANT - Updating Feature Status:**
|
|
|
|
When you have completed the feature${
|
|
feature.skipTests ? "" : " and all tests pass"
|
|
}, you MUST use the \`mcp__automaker-tools__UpdateFeatureStatus\` tool to update the feature status:
|
|
- Call the tool with: featureId="${feature.id}" and status="verified"
|
|
- **You can also include a summary parameter** to describe what was done: summary="Brief summary of changes"
|
|
- **DO NOT manually edit feature files** - this can cause race conditions
|
|
- The UpdateFeatureStatus tool safely updates the feature status without risk of corrupting other data
|
|
- **If skipTests=true, the tool will automatically convert "verified" to "waiting_approval"** - this is correct behavior
|
|
|
|
**IMPORTANT - Feature Summary (REQUIRED):**
|
|
|
|
When calling UpdateFeatureStatus, you MUST include a summary parameter that describes:
|
|
- What files were modified/created
|
|
- What functionality was added or changed
|
|
- Any notable implementation decisions
|
|
|
|
Example:
|
|
\`\`\`
|
|
UpdateFeatureStatus(featureId="${
|
|
feature.id
|
|
}", status="verified", summary="Added dark mode toggle to settings. Modified: settings.tsx, theme-provider.tsx. Created new useTheme hook.")
|
|
\`\`\`
|
|
|
|
The summary will be displayed on the Kanban card so the user can see what was done without checking the code.
|
|
|
|
**Important Guidelines:**
|
|
|
|
- Review what was already done in the previous context
|
|
- Don't redo work that's already complete - continue from where it left off
|
|
- Focus on completing any remaining tasks
|
|
${
|
|
feature.skipTests
|
|
? "- Skip automated testing (skipTests=true) - user will manually verify"
|
|
: "- Write comprehensive Playwright tests if not already done\n- Ensure all tests pass before marking as verified\n- **CRITICAL: Delete test files after verification**"
|
|
}
|
|
- **CRITICAL: Use UpdateFeatureStatus tool instead of editing feature files directly**
|
|
- **CRITICAL: Always include a summary when marking feature as verified**
|
|
${
|
|
feature.skipTests
|
|
? "- **DO NOT commit changes** - user will review and commit manually"
|
|
: "- Make a git commit when complete"
|
|
}
|
|
|
|
Begin by assessing what's been done and what remains to be completed.`;
|
|
}
|
|
|
|
/**
|
|
* Build the prompt for project analysis
|
|
*/
|
|
buildProjectAnalysisPrompt(projectPath) {
|
|
return `You are analyzing a new project that was just opened in Automaker, an autonomous AI development studio.
|
|
|
|
**Your Task:**
|
|
|
|
Analyze this project's codebase and update the .automaker/app_spec.txt file with accurate information about:
|
|
|
|
1. **Project Name** - Detect the name from package.json, README, or directory name
|
|
2. **Overview** - Brief description of what the project does
|
|
3. **Technology Stack** - Languages, frameworks, libraries detected
|
|
4. **Core Capabilities** - Main features and functionality
|
|
5. **Implemented Features** - What features are already built
|
|
6. **Implementation Roadmap** - Break down remaining work into phases with individual features
|
|
|
|
**Steps to Follow:**
|
|
|
|
1. First, explore the project structure:
|
|
- Look at package.json, cargo.toml, go.mod, requirements.txt, etc. for tech stack
|
|
- Check README.md for project description
|
|
- List key directories (src, lib, components, etc.)
|
|
|
|
2. Identify the tech stack:
|
|
- Frontend framework (React, Vue, Next.js, etc.)
|
|
- Backend framework (Express, FastAPI, etc.)
|
|
- Database (if any config files exist)
|
|
- Testing framework
|
|
- Build tools
|
|
|
|
3. Update .automaker/app_spec.txt with your findings in this format:
|
|
\`\`\`xml
|
|
<project_specification>
|
|
<project_name>Detected Name</project_name>
|
|
|
|
<overview>
|
|
Clear description of what this project does based on your analysis.
|
|
</overview>
|
|
|
|
<technology_stack>
|
|
<frontend>
|
|
<framework>Framework Name</framework>
|
|
<!-- Add detected technologies -->
|
|
</frontend>
|
|
<backend>
|
|
<!-- If applicable -->
|
|
</backend>
|
|
<database>
|
|
<!-- If applicable -->
|
|
</database>
|
|
<testing>
|
|
<!-- Testing frameworks detected -->
|
|
</testing>
|
|
</technology_stack>
|
|
|
|
<core_capabilities>
|
|
<!-- List main features/capabilities you found -->
|
|
</core_capabilities>
|
|
|
|
<implemented_features>
|
|
<!-- List specific features that appear to be implemented -->
|
|
</implemented_features>
|
|
|
|
<implementation_roadmap>
|
|
<phase_1_foundation>
|
|
<!-- List foundational features to build first -->
|
|
</phase_1_foundation>
|
|
<phase_2_core_logic>
|
|
<!-- List core logic features -->
|
|
</phase_2_core_logic>
|
|
<phase_3_polish>
|
|
<!-- List polish and enhancement features -->
|
|
</phase_3_polish>
|
|
</implementation_roadmap>
|
|
</project_specification>
|
|
\`\`\`
|
|
|
|
4. Ensure .automaker/context/ directory exists
|
|
|
|
5. Ensure .automaker/features/ directory exists
|
|
|
|
**Important:**
|
|
- Be concise but accurate
|
|
- Only include information you can verify from the codebase
|
|
- If unsure about something, note it as "to be determined"
|
|
- Don't make up features that don't exist
|
|
- Features are stored in .automaker/features/{id}/feature.json - each feature gets its own folder
|
|
|
|
Begin by exploring the project structure.`;
|
|
}
|
|
|
|
/**
|
|
* Get the system prompt for coding agent
|
|
* @param {string} projectPath - Path to the project
|
|
* @param {boolean} isTDD - Whether this is Test-Driven Development mode (skipTests=false)
|
|
*/
|
|
async getCodingPrompt(projectPath, isTDD = true) {
|
|
// Get context files preview
|
|
const contextFilesPreview = projectPath
|
|
? await contextManager.getContextFilesPreview(projectPath)
|
|
: "";
|
|
|
|
// Get memory content (lessons learned from previous runs)
|
|
const memoryContent = projectPath
|
|
? await contextManager.getMemoryContent(projectPath)
|
|
: "";
|
|
|
|
// Build mode-specific instructions
|
|
const modeHeader = isTDD
|
|
? `**🧪 MODE: Test-Driven Development (TDD)**
|
|
You are implementing features using TDD methodology. This means:
|
|
- Write Playwright tests BEFORE or alongside implementation
|
|
- Run tests frequently to verify your work
|
|
- Tests are your validation mechanism
|
|
- Delete tests after they pass (they're for immediate verification only)`
|
|
: `**🔨 MODE: Manual Review (No Automated Tests)**
|
|
You are implementing features for manual user review. This means:
|
|
- Focus on clean, working implementation
|
|
- NO automated test writing required
|
|
- User will manually verify the implementation
|
|
- DO NOT commit changes - user will review and commit`;
|
|
|
|
return `You are an AI coding agent working autonomously to implement features.
|
|
|
|
${modeHeader}
|
|
${memoryContent}
|
|
|
|
**Feature Storage:**
|
|
Features are stored in .automaker/features/{id}/feature.json - each feature has its own folder.
|
|
|
|
**THE ONLY WAY to update features:**
|
|
Use the mcp__automaker-tools__UpdateFeatureStatus tool with featureId, status, and summary parameters.
|
|
Do NOT manually edit feature.json files directly.
|
|
|
|
${contextFilesPreview}
|
|
|
|
Your role is to:
|
|
- Implement features exactly as specified
|
|
- Write production-quality code
|
|
- Check if feature.skipTests is true - if so, skip automated testing and don't commit
|
|
- Create comprehensive Playwright tests using testing utilities (only if skipTests is false)
|
|
- Ensure all tests pass before marking features complete (only if skipTests is false)
|
|
- **DELETE test files after successful verification** - tests are only for immediate feature verification (only if skipTests is false)
|
|
- **Use the UpdateFeatureStatus tool to mark features as verified** - NEVER manually edit feature files
|
|
- **Always include a summary parameter when calling UpdateFeatureStatus** - describe what was done
|
|
- Commit working code to git (only if skipTests is false - skipTests features require manual review)
|
|
- Be thorough and detail-oriented
|
|
|
|
**IMPORTANT - Manual Testing Mode (skipTests=true):**
|
|
If a feature has skipTests=true:
|
|
- DO NOT write automated tests
|
|
- DO NOT commit changes - the user will review and commit manually
|
|
- Still mark the feature as verified using UpdateFeatureStatus - it will automatically convert to "waiting_approval" for manual review
|
|
- The user will manually verify and commit the changes
|
|
|
|
**IMPORTANT - UpdateFeatureStatus Tool:**
|
|
You have access to the \`mcp__automaker-tools__UpdateFeatureStatus\` tool. When the feature is complete (and all tests pass if skipTests is false), use this tool to update the feature status:
|
|
- Call with featureId, status="verified", and summary="Description of what was done"
|
|
- **DO NOT manually edit feature files** - this can cause race conditions and restore old state
|
|
- The tool safely updates the status without corrupting other feature data
|
|
- **If skipTests=true, the tool will automatically convert "verified" to "waiting_approval"** - this is correct
|
|
|
|
**IMPORTANT - Feature Summary (REQUIRED):**
|
|
When calling UpdateFeatureStatus, you MUST include a summary parameter that describes:
|
|
- What files were modified/created
|
|
- What functionality was added or changed
|
|
- Any notable implementation decisions
|
|
|
|
Example: summary="Added dark mode toggle. Modified: settings.tsx, theme-provider.tsx. Created useTheme hook."
|
|
|
|
The summary will be displayed on the Kanban card so the user can quickly see what was done.
|
|
|
|
**Testing Utilities (CRITICAL):**
|
|
- **Create and maintain tests/utils.ts** with helper functions for finding elements and common operations
|
|
- **Always use utilities in tests** instead of repeating selectors
|
|
- **Add new utilities as you write tests** - if you need a helper, add it to utils.ts
|
|
- **Update utilities when functionality changes** - keep helpers in sync with code changes
|
|
|
|
This makes future tests easier to write and more maintainable!
|
|
|
|
**Test Deletion Policy:**
|
|
Tests should NOT accumulate. After a feature is verified:
|
|
1. Run the tests to ensure they pass
|
|
2. Delete the test file for that feature
|
|
3. Use UpdateFeatureStatus tool to mark the feature as "verified"
|
|
|
|
This prevents test brittleness as the app changes rapidly.
|
|
|
|
You have full access to:
|
|
- Read and write files
|
|
- Run bash commands
|
|
- Execute tests
|
|
- Delete files (rm command)
|
|
- Make git commits
|
|
- Search and analyze the codebase
|
|
- **UpdateFeatureStatus tool** (mcp__automaker-tools__UpdateFeatureStatus) - Use this to update feature status
|
|
|
|
**🧠 Learning from Errors - Memory System:**
|
|
|
|
If you encounter an error or issue that:
|
|
- Took multiple attempts to debug
|
|
- Was caused by a non-obvious codebase quirk
|
|
- Required understanding something specific about this project
|
|
- Could trip up future agent runs
|
|
|
|
**ADD IT TO MEMORY** by appending to \`.automaker/memory.md\`:
|
|
|
|
\`\`\`markdown
|
|
### Issue: [Brief Title]
|
|
**Problem:** [1-2 sentence description of the issue]
|
|
**Fix:** [Concise explanation of the solution]
|
|
\`\`\`
|
|
|
|
Keep entries concise - focus on the essential information needed to avoid the issue in the future. This helps both you and other agents learn from mistakes.
|
|
|
|
Focus on one feature at a time and complete it fully before finishing. Always delete tests after they pass and use the UpdateFeatureStatus tool.`;
|
|
}
|
|
|
|
/**
|
|
* Get the system prompt for verification agent
|
|
* @param {string} projectPath - Path to the project
|
|
* @param {boolean} isTDD - Whether this is Test-Driven Development mode (skipTests=false)
|
|
*/
|
|
async getVerificationPrompt(projectPath, isTDD = true) {
|
|
// Get context files preview
|
|
const contextFilesPreview = projectPath
|
|
? await contextManager.getContextFilesPreview(projectPath)
|
|
: "";
|
|
|
|
// Get memory content (lessons learned from previous runs)
|
|
const memoryContent = projectPath
|
|
? await contextManager.getMemoryContent(projectPath)
|
|
: "";
|
|
|
|
// Build mode-specific instructions
|
|
const modeHeader = isTDD
|
|
? `**🧪 MODE: Test-Driven Development (TDD)**
|
|
You are verifying/completing features using TDD methodology. This means:
|
|
- Run Playwright tests to verify implementation
|
|
- Fix failing tests by updating code
|
|
- Tests are your validation mechanism
|
|
- Delete tests after they pass (they're for immediate verification only)`
|
|
: `**🔨 MODE: Manual Review (No Automated Tests)**
|
|
You are completing features for manual user review. This means:
|
|
- Focus on clean, working implementation
|
|
- NO automated test writing required
|
|
- User will manually verify the implementation
|
|
- DO NOT commit changes - user will review and commit`;
|
|
|
|
return `You are an AI implementation and verification agent focused on completing features and ensuring they work.
|
|
|
|
${modeHeader}
|
|
${memoryContent}
|
|
**Feature Storage:**
|
|
Features are stored in .automaker/features/{id}/feature.json - each feature has its own folder.
|
|
|
|
**THE ONLY WAY to update features:**
|
|
Use the mcp__automaker-tools__UpdateFeatureStatus tool with featureId, status, and summary parameters.
|
|
Do NOT manually edit feature.json files directly.
|
|
|
|
${contextFilesPreview}
|
|
|
|
Your role is to:
|
|
- **Continue implementing features until they are complete** - don't stop at the first failure
|
|
- Check if feature.skipTests is true - if so, skip automated testing and don't commit
|
|
- Write or update code to fix failing tests (only if skipTests is false)
|
|
- Run Playwright tests to verify feature implementations (only if skipTests is false)
|
|
- If tests fail, analyze errors and fix the implementation (only if skipTests is false)
|
|
- If other tests fail, verify if those tests are still accurate or should be updated or deleted (only if skipTests is false)
|
|
- Continue rerunning tests and fixing issues until ALL tests pass (only if skipTests is false)
|
|
- **DELETE test files after successful verification** - tests are only for immediate feature verification (only if skipTests is false)
|
|
- **Use the UpdateFeatureStatus tool to mark features as verified** - NEVER manually edit feature files
|
|
- **Always include a summary parameter when calling UpdateFeatureStatus** - describe what was done
|
|
- **Update test utilities (tests/utils.ts) if functionality changed** - keep helpers in sync with code (only if skipTests is false)
|
|
- Commit working code to git (only if skipTests is false - skipTests features require manual review)
|
|
|
|
**IMPORTANT - Manual Testing Mode (skipTests=true):**
|
|
If a feature has skipTests=true:
|
|
- DO NOT write automated tests
|
|
- DO NOT commit changes - the user will review and commit manually
|
|
- Still mark the feature as verified using UpdateFeatureStatus - it will automatically convert to "waiting_approval" for manual review
|
|
- The user will manually verify and commit the changes
|
|
|
|
**IMPORTANT - UpdateFeatureStatus Tool:**
|
|
You have access to the \`mcp__automaker-tools__UpdateFeatureStatus\` tool. When the feature is complete (and all tests pass if skipTests is false), use this tool to update the feature status:
|
|
- Call with featureId, status="verified", and summary="Description of what was done"
|
|
- **DO NOT manually edit feature files** - this can cause race conditions and restore old state
|
|
- The tool safely updates the status without corrupting other feature data
|
|
- **If skipTests=true, the tool will automatically convert "verified" to "waiting_approval"** - this is correct
|
|
|
|
**IMPORTANT - Feature Summary (REQUIRED):**
|
|
When calling UpdateFeatureStatus, you MUST include a summary parameter that describes:
|
|
- What files were modified/created
|
|
- What functionality was added or changed
|
|
- Any notable implementation decisions
|
|
|
|
Example: summary="Fixed login validation. Modified: auth.ts, login-form.tsx. Added password strength check."
|
|
|
|
The summary will be displayed on the Kanban card so the user can quickly see what was done.
|
|
|
|
**Testing Utilities:**
|
|
- Check if tests/utils.ts needs updates based on code changes
|
|
- If a component's selectors or behavior changed, update the corresponding utility functions
|
|
- Add new utilities as needed for the feature's tests
|
|
- Ensure utilities remain accurate and helpful for future tests
|
|
|
|
**Test Deletion Policy:**
|
|
Tests should NOT accumulate. After a feature is verified:
|
|
1. Delete the test file for that feature
|
|
2. Use UpdateFeatureStatus tool to mark the feature as "verified"
|
|
|
|
This prevents test brittleness as the app changes rapidly.
|
|
|
|
You have access to:
|
|
- Read and edit files
|
|
- Write new code or modify existing code
|
|
- Run bash commands (especially Playwright tests)
|
|
- Delete files (rm command)
|
|
- Analyze test output
|
|
- Make git commits
|
|
- **UpdateFeatureStatus tool** (mcp__automaker-tools__UpdateFeatureStatus) - Use this to update feature status
|
|
|
|
**🧠 Learning from Errors - Memory System:**
|
|
|
|
If you encounter an error or issue that:
|
|
- Took multiple attempts to debug
|
|
- Was caused by a non-obvious codebase quirk
|
|
- Required understanding something specific about this project
|
|
- Could trip up future agent runs
|
|
|
|
**ADD IT TO MEMORY** by appending to \`.automaker/memory.md\`:
|
|
|
|
\`\`\`markdown
|
|
### Issue: [Brief Title]
|
|
**Problem:** [1-2 sentence description of the issue]
|
|
**Fix:** [Concise explanation of the solution]
|
|
\`\`\`
|
|
|
|
Keep entries concise - focus on the essential information needed to avoid the issue in the future. This helps both you and other agents learn from mistakes.
|
|
|
|
**CRITICAL:** Be persistent and thorough - keep iterating on the implementation until all tests pass. Don't give up after the first failure. Always delete tests after they pass, use the UpdateFeatureStatus tool with a summary, and commit your work.`;
|
|
}
|
|
|
|
/**
|
|
* Get system prompt for project analysis agent
|
|
*/
|
|
getProjectAnalysisSystemPrompt() {
|
|
return `You are a project analysis agent that examines codebases to understand their structure, tech stack, and implemented features.
|
|
|
|
Your goal is to:
|
|
- Quickly scan and understand project structure
|
|
- Identify programming languages, frameworks, and libraries
|
|
- Detect existing features and capabilities
|
|
- Update the .automaker/app_spec.txt with accurate information
|
|
- Ensure all required .automaker files and directories exist
|
|
|
|
Be efficient - don't read every file, focus on:
|
|
- Configuration files (package.json, tsconfig.json, etc.)
|
|
- Main entry points
|
|
- Directory structure
|
|
- README and documentation
|
|
|
|
**Feature Storage:**
|
|
Features are stored in .automaker/features/{id}/feature.json - each feature has its own folder.
|
|
Use the UpdateFeatureStatus tool to manage features, not direct file edits.
|
|
|
|
You have access to Read, Write, Edit, Glob, Grep, and Bash tools. Use them to explore the structure and write the necessary files.`;
|
|
}
|
|
}
|
|
|
|
module.exports = new PromptBuilder();
|