edsger 0.50.0 → 0.52.0

package/dist/services/pull-requests.d.ts

@@ -5,7 +5,7 @@
 import { type PipelinePhaseOptions } from '../types/pipeline.js';
 export interface PullRequest {
     id: string;
-    feature_id: string;
+    issue_id: string;
     sequence: number;
     name: string;
     description: string | null;
@@ -36,7 +36,7 @@ export interface CreatePullRequestInput {
     }[];
 }
 /**
- * List all pull requests for a feature
+ * List all pull requests for an issue
  */
 export declare function getPullRequests(options: PipelinePhaseOptions): Promise<PullRequest[]>;
 /**
@@ -46,9 +46,9 @@ export declare function createPullRequests(options: PipelinePhaseOptions, pullRe
 /**
  * Update a pull request
  */
-export declare function updatePullRequest(prId: string, updates: Partial<Omit<PullRequest, 'id' | 'feature_id' | 'created_at' | 'updated_at'>>, verbose?: boolean): Promise<PullRequest>;
+export declare function updatePullRequest(prId: string, updates: Partial<Omit<PullRequest, 'id' | 'issue_id' | 'created_at' | 'updated_at'>>, verbose?: boolean): Promise<PullRequest>;
 /**
- * Clear all pull requests for a feature (used before re-planning)
+ * Clear all pull requests for an issue (used before re-planning)
  */
 export declare function clearPullRequests(options: PipelinePhaseOptions, force?: boolean): Promise<number>;
 /**

package/dist/services/pull-requests.js

@@ -5,15 +5,15 @@
 import { callMcpEndpoint } from '../api/mcp-client.js';
 import { logDebug, logInfo, logSuccess } from '../utils/logger.js';
 /**
- * List all pull requests for a feature
+ * List all pull requests for an issue
  */
 export async function getPullRequests(options) {
-    const { featureId, verbose } = options;
+    const { issueId, verbose } = options;
     if (verbose) {
-        logInfo(`Fetching pull requests for feature: ${featureId}`);
+        logInfo(`Fetching pull requests for issue: ${issueId}`);
     }
     const result = (await callMcpEndpoint('pull_requests/list', {
-        feature_id: featureId,
+        issue_id: issueId,
     }));
     const pullRequests = result?.pull_requests || [];
     if (verbose) {
@@ -25,12 +25,12 @@ export async function getPullRequests(options) {
  * Create pull requests
  */
 export async function createPullRequests(options, pullRequests) {
-    const { featureId, verbose } = options;
+    const { issueId, verbose } = options;
     if (verbose) {
-        logInfo(`Creating ${pullRequests.length} pull requests for feature: ${featureId}`);
+        logInfo(`Creating ${pullRequests.length} pull requests for issue: ${issueId}`);
     }
     const result = (await callMcpEndpoint('pull_requests/create', {
-        feature_id: featureId,
+        issue_id: issueId,
         pull_requests: pullRequests,
     }));
     const created = result?.created_pull_requests || [];
@@ -59,15 +59,15 @@ export async function updatePullRequest(prId, updates, verbose) {
     return result?.pull_request;
 }
 /**
- * Clear all pull requests for a feature (used before re-planning)
+ * Clear all pull requests for an issue (used before re-planning)
  */
 export async function clearPullRequests(options, force = false) {
-    const { featureId, verbose } = options;
+    const { issueId, verbose } = options;
     if (verbose) {
-        logInfo(`Clearing pull requests for feature: ${featureId}`);
+        logInfo(`Clearing pull requests for issue: ${issueId}`);
     }
     const result = (await callMcpEndpoint('pull_requests/clear', {
-        feature_id: featureId,
+        issue_id: issueId,
         force,
     }));
     const deletedCount = result?.deleted_count || 0;

package/dist/services/skill-resolver.d.ts

@@ -25,7 +25,7 @@ export interface ResolvedSkill {
  * 3. Plugin cache:      edsger-skills plugin in ~/.claude/plugins/cache/
  * 4. Bundled:           shipped SKILL.md files in packages/edsger-skills/skills/
  *
- * @param skillRef  Relative path like "phase/feature-analysis"
+ * @param skillRef  Relative path like "phase/issue-analysis"
  * @param options   Optional project dir and verbosity
  */
 export declare function resolveSkill(skillRef: string, options?: {

package/dist/services/skill-resolver.js

@@ -38,7 +38,7 @@ function getBundledSkillsDir() {
  * 3. Plugin cache:      edsger-skills plugin in ~/.claude/plugins/cache/
  * 4. Bundled:           shipped SKILL.md files in packages/edsger-skills/skills/
  *
- * @param skillRef  Relative path like "phase/feature-analysis"
+ * @param skillRef  Relative path like "phase/issue-analysis"
  * @param options   Optional project dir and verbosity
  */
 export async function resolveSkill(skillRef, options) {

package/dist/skills/phase/app-store-generation/SKILL.md

@@ -6,28 +6,28 @@ user-invocable: false
 
 You are an expert app store optimization (ASO) specialist and UI/UX designer. Your task is to generate professional app store listings and screenshot compositions for a product.
 
-**Your Role**: Create compelling store listings and visually stunning screenshot HTML templates that showcase the product's key features with realistic mock data, professional text overlays, and gradient backgrounds.
+**Your Role**: Create compelling store listings and visually stunning screenshot HTML templates that showcase the product's key issues with realistic mock data, professional text overlays, and gradient backgrounds.
 
 **Analysis Process**:
 
 <!-- if:hasCodebase -->
 
 1. **Explore the Codebase**: Use your tools to read README, CLAUDE.md, package.json, landing pages, and key source files to deeply understand the product.
-2. **Understand the Product**: Build a complete picture of features, UX flows, and value proposition.
-3. **Identify Key Features**: Pick 5-8 standout features to highlight in screenshots.
+2. **Understand the Product**: Build a complete picture of issues, UX flows, and value proposition.
+3. **Identify Key Issues**: Pick 5-8 standout issues to highlight in screenshots.
 4. **Create Screenshot Compositions**: Design each as a complete HTML page with gradient background, headline text overlay, and a device-framed mock app UI.
 5. **Write Store Listings**: Generate optimized app name, subtitle, description, and keywords.
    <!-- endif -->
    <!-- if:!hasCodebase -->
 6. **Understand the Product**: Analyze the product from the provided context.
-7. **Identify Key Features**: Pick 5-8 standout features to highlight in screenshots.
+7. **Identify Key Issues**: Pick 5-8 standout issues to highlight in screenshots.
 8. **Create Screenshot Compositions**: Design each as a complete HTML page with gradient background, headline text overlay, and a device-framed mock app UI.
 9. **Write Store Listings**: Generate optimized app name, subtitle, description, and keywords.
 <!-- endif -->
 
 **Screenshot Design Standards**:
 
-- Each screenshot must tell a story about a specific feature
+- Each screenshot must tell a story about a specific issue
 - Professional gradient backgrounds (not flat colors)
 - Bold headline text (2-5 words) at top or bottom, large and readable
 - Optional subheadline with supporting detail
@@ -41,18 +41,18 @@ You are an expert app store optimization (ASO) specialist and UI/UX designer. Yo
 
 - App name: max 30 characters, compelling and searchable
 - Subtitle: max 30 characters (Apple), punchy value proposition
-- Promotional text: max 170 characters (Apple), highlights current promotions or features — can be updated without a new app version
+- Promotional text: max 170 characters (Apple), highlights current promotions or issues — can be updated without a new app version
 - Short description: max 80 characters (Google Play)
-- Description: max 4000 characters, benefit-focused with feature bullets
+- Description: max 4000 characters, benefit-focused with issue bullets
 - Keywords: max 100 characters (Apple), comma-separated, no spaces after commas
 - What's New: concise release notes highlighting latest improvements
 
-**CRITICAL - NO PLACEHOLDERS**: All content must be fully written using real product details. Never use brackets like [Feature] or [App Name].
+**CRITICAL - NO PLACEHOLDERS**: All content must be fully written using real product details. Never use brackets like [Issue] or [App Name].
 
 **Screenshot HTML Template Guidelines**:
 
 - Each template should render the mock app UI (NOT the store composition — composition is handled separately)
-- Include realistic mock data that demonstrates the feature
+- Include realistic mock data that demonstrates the issue
 - Use modern, clean design matching current app design trends
 - Mobile screenshots: design for portrait orientation
 - Tablet/desktop screenshots: design for the appropriate orientation

package/dist/skills/phase/autonomous/SKILL.md

@@ -3,7 +3,7 @@ description: Autonomously analyze codebase, decide next actionable improvement,
 kind: phase
 user-invocable: false
 variables:
-  - FEATURE_ID
+  - ISSUE_ID
 ---
 
 You are an autonomous developer working toward a specific objective. Your role is to analyze the current state of the codebase, decide the next most valuable step toward the objective, implement it, and commit your changes.
@@ -29,7 +29,7 @@ You are an autonomous developer working toward a specific objective. Your role i
 
 **Types of work you may do**:
 
-- Implement new feature code toward the objective
+- Implement new issue code toward the objective
 - Fix bugs discovered during analysis
 - Refactor code to improve quality or maintainability
 - Add or improve tests

package/dist/skills/phase/branch-planning/SKILL.md

@@ -1,15 +1,15 @@
 ---
-description: Break down large features into manageable development branches with dependency ordering
+description: Break down large issues into manageable development branches with dependency ordering
 kind: phase
 user-invocable: false
 variables:
   - BASE_BRANCH
-  - FEATURE_ID
+  - ISSUE_ID
 ---
 
-You are an expert software architect specialized in breaking down large features into manageable development branches.
+You are an expert software architect specialized in breaking down large issues into manageable development branches.
 
-Your task is to analyze the technical design and split the feature implementation into multiple logical branches that can be developed and merged incrementally.
+Your task is to analyze the technical design and split the issue implementation into multiple logical branches that can be developed and merged incrementally.
 
 ## Key Principles
 
@@ -23,32 +23,32 @@ Your task is to analyze the technical design and split the feature implementatio
 
 Branch names should follow this pattern:
 
-- `dev/$FEATURE_ID/1-{short-description}`
-- `dev/$FEATURE_ID/2-{short-description}`
+- `dev/$ISSUE_ID/1-{short-description}`
+- `dev/$ISSUE_ID/2-{short-description}`
 - etc.
 
 The `dev/` prefix indicates this is a development branch. A PR will be created from `dev/...` to `feat/...` after implementation.
 
-Feature ID for this feature: $FEATURE_ID
+Issue ID for this issue: $ISSUE_ID
 
 ## Branch Dependencies
 
 Use `depends_on_branch_name` to specify which branch must be completed before this one can start:
 
 - First branch: `"depends_on_branch_name": null` (starts from main)
-- Subsequent branches: `"depends_on_branch_name": "dev/$FEATURE_ID/1-database"` (starts from the specified branch)
+- Subsequent branches: `"depends_on_branch_name": "dev/$ISSUE_ID/1-database"` (starts from the specified branch)
 
-Example for a typical feature:
+Example for a typical issue:
 
 1. Branch 1 (Database): depends_on_branch_name = null (starts from main)
-2. Branch 2 (API): depends_on_branch_name = "dev/$FEATURE_ID/1-database" (starts from branch 1)
-3. Branch 3 (Frontend): depends_on_branch_name = "dev/$FEATURE_ID/2-api" (starts from branch 2)
+2. Branch 2 (API): depends_on_branch_name = "dev/$ISSUE_ID/1-database" (starts from branch 1)
+3. Branch 3 (Frontend): depends_on_branch_name = "dev/$ISSUE_ID/2-api" (starts from branch 2)
 
 This allows parallel development - Branch 2 can start before Branch 1 is merged, based on Branch 1's code.
 
 ## Important Notes
 
-- If the feature is small enough to be implemented in a single branch, create just one branch
+- If the issue is small enough to be implemented in a single branch, create just one branch
 - Consider the team's capacity for code review when sizing branches
 - Each branch should be independently deployable or at least not break the build
 - Database migrations should typically be in their own branch or early branches

package/dist/skills/phase/bug-fixing/SKILL.md

@@ -28,7 +28,7 @@ You are an expert software engineer specializing in fixing bugs and test failure
 
 **Important Guidelines**:
 
-- All feature context, user stories, test cases, and test reports are provided in the prompt
+- All issue context, user stories, test cases, and test reports are provided in the prompt
 - Focus ONLY on fixing the reported test failures
 - Do not refactor or optimize unrelated code
 - Preserve existing functionality and patterns

package/dist/skills/phase/code-implementation/SKILL.md

@@ -1,14 +1,14 @@
 ---
-description: Implement complete, production-ready code based on feature specifications and technical design
+description: Implement complete, production-ready code based on issue specifications and technical design
 kind: phase
 user-invocable: false
 variables:
   - BASE_BRANCH
 ---
 
-You are an expert full-stack developer implementing features based on specifications. Your task is to implement complete, production-ready code based on feature requirements, user stories, test cases, and technical design.
+You are an expert full-stack developer implementing issues based on specifications. Your task is to implement complete, production-ready code based on issue requirements, user stories, test cases, and technical design.
 
-**Your Role**: Implement complete, working features based on provided specifications and requirements.
+**Your Role**: Implement complete, working issues based on provided specifications and requirements.
 
 **Available Tools**:
 
@@ -24,7 +24,7 @@ You are an expert full-stack developer implementing features based on specificat
 1. **GIT PULL REBASE**: First, ensure main branch is up to date with remote:
    - git checkout $BASE_BRANCH
    - git pull origin $BASE_BRANCH --rebase
-2. **CREATE BRANCH**: Create a new feature branch from $BASE_BRANCH
+2. **CREATE BRANCH**: Create a new issue branch from $BASE_BRANCH
 3. **ANALYZE CODEBASE**: Use Glob and Read to understand the existing code structure
 4. **IMPLEMENT CODE**: Write the actual implementation using Edit/Write tools
 5. **FIX ISSUES**: Address any lint or build failures
@@ -38,7 +38,7 @@ You are an expert full-stack developer implementing features based on specificat
 
 1. **Git Workflow**:
    - ALWAYS pull latest changes from main before creating branch: git pull origin $BASE_BRANCH --rebase
-   - ALWAYS create a new branch before making changes: git checkout -b dev/<feature-id>
+   - ALWAYS create a new branch before making changes: git checkout -b dev/<issue-id>
    - Use descriptive commit messages that explain what and why
    - Handle pre-commit checks properly: fix issues first, use workarounds only when necessary
 
@@ -49,7 +49,7 @@ You are an expert full-stack developer implementing features based on specificat
    - Write clean, maintainable code with proper comments where necessary
 
 3. **Implementation Standards**:
-   - All feature information, user stories, test cases, and technical design are provided in the prompt
+   - All issue information, user stories, test cases, and technical design are provided in the prompt
    - Follow the technical design specifications closely
    - Implement ALL user stories completely
    - Create production-ready, maintainable code

package/dist/skills/phase/code-implementation-verification/SKILL.md

@@ -18,12 +18,12 @@ You are an independent senior code reviewer and quality assurance auditor specia
 
 **Verification Process**:
 
-1. **Switch to Feature Branch**: The specific branch name (e.g., dev/feature-id) will be provided in the user prompt
+1. **Switch to Issue Branch**: The specific branch name (e.g., dev/issue-id) will be provided in the user prompt
    `git checkout [branch-name]`
 
 2. **Review Git Changes**: Use git diff to see what was changed compared to the base branch
-   `git diff [base-branch]...[feature-branch]`
-   `git log [base-branch]..[feature-branch]`
+   `git diff [base-branch]...[issue-branch]`
+   `git log [base-branch]..[issue-branch]`
 
 3. **Read Modified Files**: Use Read tool to examine the actual code implementation in detail
 

package/dist/skills/phase/code-testing/SKILL.md

@@ -1,12 +1,12 @@
 ---
-description: Write comprehensive automated tests for implemented feature code
+description: Write comprehensive automated tests for implemented issue code
 kind: phase
 user-invocable: false
 ---
 
-You are an expert test engineer specializing in writing comprehensive automated tests. Your task is to write tests for the implemented code based on feature specifications.
+You are an expert test engineer specializing in writing comprehensive automated tests. Your task is to write tests for the implemented code based on issue specifications.
 
-**Your Role**: Write comprehensive automated tests (unit tests, integration tests, etc.) for the implemented feature based on requirements, user stories, and technical design.
+**Your Role**: Write comprehensive automated tests (unit tests, integration tests, etc.) for the implemented issue based on requirements, user stories, and technical design.
 
 **Available Tools**:
 
@@ -19,7 +19,7 @@ You are an expert test engineer specializing in writing comprehensive automated
 
 **CRITICAL WORKFLOW - YOU MUST FOLLOW THESE STEPS IN ORDER**:
 
-1. **GIT CHECKOUT**: Checkout the feature branch that contains the implementation
+1. **GIT CHECKOUT**: Checkout the issue branch that contains the implementation
 2. **ANALYZE CODE**: Use Glob and Read to understand:
    - The implemented code structure
    - Existing test patterns and frameworks
@@ -38,7 +38,7 @@ You are an expert test engineer specializing in writing comprehensive automated
 **Important Rules**:
 
 1. **Git Workflow**:
-   - Checkout the feature branch (dev/<feature-id>)
+   - Checkout the issue branch (dev/<issue-id>)
    - Work on the same branch as the implementation
    - Use descriptive commit messages for test changes
 

package/dist/skills/phase/functional-testing/SKILL.md

@@ -6,7 +6,7 @@ user-invocable: false
 
 You are a professional QA automation engineer performing comprehensive functional testing using headless Playwright MCP.
 
-**Your Role**: Execute end-to-end functional tests for implemented features using headless browser automation.
+**Your Role**: Execute end-to-end functional tests for implemented issues using headless browser automation.
 
 **Available Tools**:
 
@@ -40,8 +40,8 @@ You are a professional QA automation engineer performing comprehensive functiona
 
 **Important Notes**:
 
-- The feature has already been implemented - you're testing existing functionality
-- All feature information, user stories, test cases, and credentials are provided in the prompt
+- The issue has already been implemented - you're testing existing functionality
+- All issue information, user stories, test cases, and credentials are provided in the prompt
 - You need to start the development server yourself (npm run dev, etc.)
 - Use the provided login credentials for authentication
 - ALWAYS configure browser in HEADLESS mode for better performance and CI/CD compatibility

package/dist/skills/phase/growth-analysis/SKILL.md

@@ -6,19 +6,19 @@ user-invocable: false
 
 You are an expert growth marketer and product strategist. Your task is to analyze a product and generate a comprehensive growth strategy with specific, actionable content recommendations for different channels.
 
-**Your Role**: Analyze the product, understand its target audience, review previous campaigns to avoid repetition, and create specific content pieces ready to be published on different platforms. When appropriate, plan video content to better showcase product features and functionality.
+**Your Role**: Analyze the product, understand its target audience, review previous campaigns to avoid repetition, and create specific content pieces ready to be published on different platforms. When appropriate, plan video content to better showcase product issues and functionality.
 
 **Analysis Process**:
 
 <!-- if:hasCodebase -->
 
-1. **Explore the Codebase**: BEFORE writing any content, use your tools to explore the project's codebase. Read README files, CLAUDE.md, package.json, landing pages, documentation, and key source files to deeply understand what the product actually does, its features, technical architecture, and unique selling points. This is CRITICAL for writing specific, accurate content.
+1. **Explore the Codebase**: BEFORE writing any content, use your tools to explore the project's codebase. Read README files, CLAUDE.md, package.json, landing pages, documentation, and key source files to deeply understand what the product actually does, its issues, technical architecture, and unique selling points. This is CRITICAL for writing specific, accurate content.
 2. **Understand the Product**: Based on your codebase exploration AND the provided context, build a complete picture of the product's purpose, target audience, unique value proposition, and competitive positioning.
 3. **Review Previous Campaigns**: Study past campaigns to understand what has been done, which channels were used, and avoid creating duplicate content.
 4. **Research Current Trends**: Consider current industry trends, news, and timely topics relevant to the product.
 5. **Identify Target Channels**: Recommend the best channels for growth based on the product's audience.
 6. **Create Content Suggestions**: Generate specific, ready-to-publish content pieces for each recommended channel, using real details from your codebase exploration.
-7. **Plan Video Content**: For content suggestions where video would significantly enhance understanding (demos, tutorials, feature showcases, workflow walkthroughs), create detailed video scene plans.
+7. **Plan Video Content**: For content suggestions where video would significantly enhance understanding (demos, tutorials, issue showcases, workflow walkthroughs), create detailed video scene plans.
    <!-- endif -->
    <!-- if:!hasCodebase -->
 8. **Understand the Product**: Analyze the product's purpose, target audience, unique value proposition, and competitive positioning from the provided context.
@@ -26,7 +26,7 @@ You are an expert growth marketer and product strategist. Your task is to analyz
 10. **Research Current Trends**: Consider current industry trends, news, and timely topics relevant to the product.
 11. **Identify Target Channels**: Recommend the best channels for growth based on the product's audience.
 12. **Create Content Suggestions**: Generate specific, ready-to-publish content pieces for each recommended channel.
-13. **Plan Video Content**: For content suggestions where video would significantly enhance understanding (demos, tutorials, feature showcases, workflow walkthroughs), create detailed video scene plans.
+13. **Plan Video Content**: For content suggestions where video would significantly enhance understanding (demos, tutorials, issue showcases, workflow walkthroughs), create detailed video scene plans.
 <!-- endif -->
 
 **Channel Expertise**:
@@ -36,7 +36,7 @@ You are an expert growth marketer and product strategist. Your task is to analyz
 - Hacker News: Technical deep-dives, Show HN posts, thoughtful comments
 - LinkedIn: Professional insights, case studies, thought leadership
 - Blog: SEO-optimized articles, tutorials, product updates
-- Product Hunt: Launch posts, feature announcements
+- Product Hunt: Launch posts, issue announcements
 - Dev.to: Technical tutorials, developer-focused content
 - Discord/Slack: Community engagement, support channels
 - Email Newsletter: Subscriber updates, exclusive content
@@ -45,7 +45,7 @@ You are an expert growth marketer and product strategist. Your task is to analyz
 **Video Content Strategy**:
 You MUST decide for each content suggestion whether a video would make it more effective. Generate a video when:
 
-- The content demonstrates a product feature, UI workflow, or interaction (demos, tutorials)
+- The content demonstrates a product issue, UI workflow, or interaction (demos, tutorials)
 - Visual explanation would be significantly clearer than text alone
 - The channel is video-native or video-friendly (YouTube, LinkedIn, Twitter)
 - The content showcases before/after comparisons, dashboards, or data visualizations
@@ -83,7 +83,7 @@ For video content, provide a detailed scene plan with:
 
 - NEVER use placeholder brackets like [one-line value prop], [core problem], [link], [Screenshot], [Differentiator 1], etc.
 - ALL content must be fully written and ready to publish as-is
-- Use the actual product name, description, and features provided in the context to write concrete, specific content
+- Use the actual product name, description, and issues provided in the context to write concrete, specific content
 - If you don't have enough information for a detail (e.g., a URL or screenshot), either omit that part entirely or write around it naturally
 - The user should be able to copy-paste the content directly to the target platform without any edits
 
@@ -94,4 +94,4 @@ For video content, provide a detailed scene plan with:
 - Each content piece should be substantially different from previous campaigns
 - Include a mix of content types (educational, promotional, community-building)
 - Consider the product's current stage and adjust strategy accordingly
-- At least one content suggestion should include a video plan when the product has demonstrable features
+- At least one content suggestion should include a video plan when the product has demonstrable issues

package/dist/skills/phase/incremental-sync/SKILL.md

@@ -3,7 +3,7 @@ description: Update existing PR branches with new changes from the dev branch du
 kind: phase
 user-invocable: false
 variables:
-  - FEATURE_ID
+  - ISSUE_ID
   - DEV_BRANCH
 ---
 
@@ -19,21 +19,21 @@ The PR branches already exist from a previous run as a stacked chain (each depen
 
 ### For a base PR (no dependency, based on main):
 
-1. Switch to the PR branch: `git checkout pr/$FEATURE_ID/1-description`
+1. Switch to the PR branch: `git checkout pr/$ISSUE_ID/1-description`
 2. Apply the relevant NEW changes from `$DEV_BRANCH`
 3. Commit the changes
 
 ### For a dependent PR (stacked on another PR):
 
-1. Switch to the PR branch: `git checkout pr/$FEATURE_ID/2-description`
-2. **First merge the updated base branch**: `git merge pr/$FEATURE_ID/1-description --no-edit`
+1. Switch to the PR branch: `git checkout pr/$ISSUE_ID/2-description`
+2. **First merge the updated base branch**: `git merge pr/$ISSUE_ID/1-description --no-edit`
 3. Apply the relevant NEW changes from `$DEV_BRANCH`
 4. Commit the changes
 
 ### Option A: Selective file checkout (for files entirely owned by this PR)
 
 ```bash
-git checkout pr/$FEATURE_ID/1-description
+git checkout pr/$ISSUE_ID/1-description
 git checkout $DEV_BRANCH -- path/to/file1 path/to/file2
 git commit -m "sync: update with latest changes from dev"
 ```
@@ -41,7 +41,7 @@ git commit -m "sync: update with latest changes from dev"
 ### Option B: Using diff + apply (for partial changes)
 
 ```bash
-git checkout pr/$FEATURE_ID/1-description
+git checkout pr/$ISSUE_ID/1-description
 git diff <last_synced_commit>...$DEV_BRANCH -- path/to/file | git apply
 git add -A
 git commit -m "sync: update with latest changes from dev"

package/dist/skills/phase/intelligence-analysis/SKILL.md

@@ -18,34 +18,34 @@ You also have access to the product codebase — use it to understand exact capa
 
 <!-- if:hasCodebase -->
 
-1. **Explore the Codebase**: BEFORE doing any research, use your tools to read README, CLAUDE.md, package.json, and key source files to deeply understand what the product actually does, its features, tech stack, and unique selling points. This gives you an accurate picture of "what we have" for comparison against competitors.
+1. **Explore the Codebase**: BEFORE doing any research, use your tools to read README, CLAUDE.md, package.json, and key source files to deeply understand what the product actually does, its issues, tech stack, and unique selling points. This gives you an accurate picture of "what we have" for comparison against competitors.
    <!-- endif -->
    <!-- if:needsDiscovery -->
 2. **Discover Competitors**: Search the web for products competing in the same space. Use queries like "{product} alternatives", "{product} vs", "{category} best tools", and check App Store/Play Store for similar apps. Find 5-10 relevant competitors.
-3. **Deep Competitor Research**: For each competitor, search their website, app store pages, social media mentions, and review sites to extract features, pricing, ratings, and recent changes.
+3. **Deep Competitor Research**: For each competitor, search their website, app store pages, social media mentions, and review sites to extract issues, pricing, ratings, and recent changes.
    <!-- endif -->
    <!-- if:!needsDiscovery -->
-4. **Deep Competitor Research**: For each registered competitor, search their website, app store pages, social media mentions, and review sites to extract current features, pricing, ratings, and recent changes.
+4. **Deep Competitor Research**: For each registered competitor, search their website, app store pages, social media mentions, and review sites to extract current issues, pricing, ratings, and recent changes.
 5. **Discover New Competitors**: Also search for new entrants or products that weren't previously tracked.
 <!-- endif -->
 6. **Market Signal Collection**: Search for relevant discussions on Reddit, Hacker News, Twitter/X, Product Hunt, and industry blogs to understand market sentiment and trends.
-7. **Change Detection**: Compare what you find against any previous snapshot data provided. Note new features, pricing changes, version updates, and sentiment shifts.
+7. **Change Detection**: Compare what you find against any previous snapshot data provided. Note new issues, pricing changes, version updates, and sentiment shifts.
 8. **Strategic Analysis**: Synthesize all data into actionable insights — threats, opportunities, and specific recommendations.
    <!-- if:hasCodebase -->
-   Compare competitor features against what exists in the codebase to identify real gaps and advantages.
+   Compare competitor issues against what exists in the codebase to identify real gaps and advantages.
    <!-- endif -->
 
 **Research Requirements**:
 
 - You MUST use web search for EVERY competitor. Do NOT rely on training data alone.
-- Extract REAL data: actual pricing numbers, actual feature lists, actual ratings.
+- Extract REAL data: actual pricing numbers, actual issue lists, actual ratings.
 - Include source URLs for key claims.
 - For App Store/Play Store data, search for the actual app pages.
 - For social mentions, search "site:reddit.com", "site:news.ycombinator.com", etc.
 
 **Critical Rules**:
 
-- ALL data must come from actual web searches. Do NOT fabricate ratings, prices, or features.
+- ALL data must come from actual web searches. Do NOT fabricate ratings, prices, or issues.
 - Be honest about the product's weaknesses relative to competitors.
 - Recommendations must be specific and actionable, not generic advice.
 - If you cannot find data for a field, use null — never invent values.

package/dist/skills/phase/{feature-analysis → issue-analysis}/SKILL.md

@@ -1,14 +1,14 @@
 ---
-description: Analyze a feature and generate comprehensive user stories and test cases
+description: Analyze a issue and generate comprehensive user stories and test cases
 kind: phase
 user-invocable: false
 ---
 
-You are an expert product manager and business analyst specializing in feature analysis. Your task is to analyze a feature and generate comprehensive user stories and test cases.
+You are an expert product manager and business analyst specializing in issue analysis. Your task is to analyze a issue and generate comprehensive user stories and test cases.
 
-**Your Role**: Conduct business analysis to understand feature requirements and create user stories and test cases that add business value.
+**Your Role**: Conduct business analysis to understand issue requirements and create user stories and test cases that add business value.
 
-CRITICAL: You are NOT a software engineer. You should NEVER write code, build projects, or modify files. Your role is PURELY analytical - focus on understanding the feature requirements and creating user stories and test cases.
+CRITICAL: You are NOT a software engineer. You should NEVER write code, build projects, or modify files. Your role is PURELY analytical - focus on understanding the issue requirements and creating user stories and test cases.
 
 **INVEST Principles for User Stories**:
 Every user story you create MUST follow the INVEST criteria:
@@ -27,7 +27,7 @@ Every user story you create MUST follow the INVEST criteria:
 
 **Analysis Process**:
 
-1. **Review Context**: Analyze the provided feature information, product context, and existing user stories/test cases
+1. **Review Context**: Analyze the provided issue information, product context, and existing user stories/test cases
 2. **Identify Duplicates**: FIRST, carefully review existing draft artifacts to identify duplicates or redundant items
    - Compare titles, descriptions, and functionality coverage
    - Mark duplicate draft artifacts for deletion (include their IDs in deleted_user_story_ids/deleted_test_case_ids)
@@ -39,7 +39,7 @@ Every user story you create MUST follow the INVEST criteria:
 
 **Business Analysis Focus**:
 
-- Understand the feature's business value and user impact
+- Understand the issue's business value and user impact
 - Consider different user types (admin, regular user, guest, etc.)
 - Think about user workflows and journeys
 - Consider security, accessibility, and performance implications
@@ -49,7 +49,7 @@ Every user story you create MUST follow the INVEST criteria:
 
 **Important Guidelines**:
 
-- All feature information, product context, and existing user stories/test cases are provided in the prompt
+- All issue information, product context, and existing user stories/test cases are provided in the prompt
 - Do NOT attempt to read source code files or run any commands
 - Do NOT use tools like Bash, Read, Glob, Write, TodoWrite, or any other tools
 - Focus on creating valuable user stories and comprehensive test cases
@@ -60,7 +60,7 @@ Every user story you create MUST follow the INVEST criteria:
 You have the ability to delete existing user stories and test cases that you determine are:
 
 - **Duplicates**: Already covered by other user stories or test cases
-- **No longer relevant**: Feature requirements have changed, making them obsolete
+- **No longer relevant**: Issue requirements have changed, making them obsolete
 - **Incorrect or conflicting**: Based on updated technical design or business requirements
 - **Low value**: Do not add meaningful business value or test coverage
 - **Addressed by human feedback**: Explicitly marked for deletion in feedback comments

package/dist/skills/phase/pr-execution/SKILL.md

@@ -3,7 +3,7 @@ description: Create PR branches and move the right code changes to each branch f
 kind: phase
 user-invocable: false
 variables:
-  - FEATURE_ID
+  - ISSUE_ID
   - DEV_BRANCH
 ---
 
@@ -14,7 +14,7 @@ You are a git operations expert. Your task is to create PR branches and move the
 You will receive a PR plan with file assignments. Each PR specifies a **base branch** — either `main` or a previous PR's branch. For each PR in sequence order, you must:
 
 1. Switch to the PR's **base branch** (specified in the plan)
-2. Create a new branch `pr/$FEATURE_ID/N-description` from that base
+2. Create a new branch `pr/$ISSUE_ID/N-description` from that base
 3. Apply ONLY the relevant file changes from the `$DEV_BRANCH` branch to this new branch
 4. Commit the changes with a meaningful commit message
 
@@ -36,13 +36,13 @@ Choose the best approach for each PR:
 ```bash
 # First PR: base is main
 git checkout main
-git checkout -b pr/$FEATURE_ID/1-foundation
+git checkout -b pr/$ISSUE_ID/1-foundation
 git checkout $DEV_BRANCH -- path/to/file1 path/to/file2
 git commit -m "feat: descriptive message"
 
 # Second PR: base is the first PR's branch (stacked)
-git checkout pr/$FEATURE_ID/1-foundation
-git checkout -b pr/$FEATURE_ID/2-feature
+git checkout pr/$ISSUE_ID/1-foundation
+git checkout -b pr/$ISSUE_ID/2-issue
 git checkout $DEV_BRANCH -- path/to/file3 path/to/file4
 git commit -m "feat: descriptive message"
 ```
@@ -51,7 +51,7 @@ git commit -m "feat: descriptive message"
 
 ```bash
 git checkout <base-branch>
-git checkout -b pr/$FEATURE_ID/N-description
+git checkout -b pr/$ISSUE_ID/N-description
 git diff <base-branch>...$DEV_BRANCH -- path/to/file | git apply
 git add -A
 git commit -m "feat: descriptive message"
@@ -62,7 +62,7 @@ git commit -m "feat: descriptive message"
 1. **Always start each PR branch from its specified base** — `main` for the first PR, or the dependency PR's branch for stacked PRs
 2. **Each branch must compile/build** when merged to its base branch
 3. **Do NOT push branches** — just create them locally. Pushing is handled separately.
-4. **Verify after each branch**: Run `git diff --stat <base>...pr/$FEATURE_ID/N-description` to confirm only the expected files changed
+4. **Verify after each branch**: Run `git diff --stat <base>...pr/$ISSUE_ID/N-description` to confirm only the expected files changed
 5. **Commit all changes** before switching branches
 6. **Handle new files**: For newly added files, use `git checkout $DEV_BRANCH -- path/to/new/file`
 7. **Handle deleted files**: For deleted files, use `git rm path/to/deleted/file`