implement-pb
Implement actionable items from a review - pick items by number, implement them, and mark them as resolved in the review document.
What this skill does
<purpose>
Implement specific actionable items from a review document. Load the review, show remaining items, let the user pick which to implement, do the work, and update the review doc as items are resolved.
</purpose>
<steps>
<step id="load-config" number="1">
<description>Load Configuration</description>
<load-config>
<action>Resolve the user's home directory.</action>
<command language="bash" output="home" tool="Bash">echo $HOME</command>
<constraint>Never pass `~` to the Read tool.</constraint>
<read path="<home>/.things/config.json" output="config" />
<if condition="config-missing">Tell the user: "Run `/things:setup-things` first." Then stop.<exit /></if>
<read path="<home>/.things/playbook/preferences.json" output="preferences" />
<if condition="preferences-missing">Tell the user: "Run `/setup-pb` first." Then stop.<exit /></if>
</load-config>
</step>
<step id="find-review" number="2">
<description>Find Review</description>
<if condition="argument-is-review-filename-or-slug">
<read path="<home>/.things/playbook/reviews/<review>.md" output="review" />
</if>
<if condition="argument-not-a-review">
<action>List recent reviews from `<home>/.things/playbook/reviews/` (sorted by date, most recent first).</action>
<ask-user-question>
<question>Which review would you like to implement items from?</question>
</ask-user-question>
<read path="<home>/.things/playbook/reviews/<selected>.md" output="review" />
</if>
</step>
<step id="show-actionable-items" number="3">
<description>Show Remaining Actionable Items</description>
<action>Parse the review's "Actionable Items" section. Show a numbered list:</action>
<output>
Actionable items from: <review title>
1. <item title> -- <what's needed> (priority: <priority>)
2. <item title> -- <what's needed> (priority: <priority>)
...
</output>
<if condition="no-actionable-items">
<action>Tell the user: "All items in this review have been addressed!" Then stop.</action>
</if>
<ask-user-question>
<question>Which items would you like to implement? Enter numbers (e.g., "1", "1,3", "1-3"), or "all".</question>
</ask-user-question>
</step>
<step id="implement-items" number="4">
<description>Implement Selected Items</description>
<action>For each selected item:</action>
1. Read the item's context (what's needed, relevant context from the review)
2. Implement the action using available tools
3. Mark the item as resolved in the review document
<constraint>After completing each item, briefly confirm what was done before moving to the next.</constraint>
<constraint>If an item can't be fully implemented (blocked, needs external input), explain why and leave it as actionable.</constraint>
</step>
<step id="update-review" number="5">
<description>Update Review Document</description>
<action>For each completed item:</action>
- Move it from "Actionable Items" to "Done" section with evidence of completion
- Decrement `actionable_count` in frontmatter
- Increment `done_count` in frontmatter
- If all items resolved, update `status` to `"all-addressed"`
<write path="<home>/.things/playbook/reviews/<review>.md" content="updated-review" />
</step>
<step id="git-workflow" number="6">
<description>Handle Git Workflow</description>
<git-workflow>
<action>Read git workflow from `config.json` (`git.workflow`).</action>
<if condition="workflow-auto">Automatically `git add`, `git commit -m "implement: <N> items from <review>"`, and `git push`.</if>
<if condition="workflow-ask">
<ask-user-question>
<question>Commit and push the updated review?</question>
<option>Yes -- commit and push</option>
<option>Commit only</option>
<option>No -- I'll handle git myself</option>
</ask-user-question>
</if>
<if condition="workflow-manual">Tell the user the review has been updated.</if>
</git-workflow>
</step>
<step id="confirm" number="7">
<description>Confirm</description>
<completion-message>
Implemented <N> items from: **<review title>**
Remaining actionable: <actionable_count>
<if condition="all-implemented">All items resolved! Consider running `/playbook:update-pb <plan> --status completed`.</if>
<if condition="has-remaining">Run `/implement-pb <review>` again to continue.</if>
</completion-message>
</step>
</steps>
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.