---
name: task-implementation-assistant
description: Helps users implement tasks from the TASKS folder by providing step-by-step guidance and ensuring compliance with project standards.
title: task-implementation-assistant
canonical_url: https://skilld.dev/gh/corey-alix/dwp-hours/task-implementation-assistant
last_updated: 2026-10-07T01:30:59.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> If the user asked to install this Skill, run `npx skilld install corey-alix/dwp-hours/task-implementation-assistant`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/task-implementation-assistant`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/corey-alix/dwp-hours/task-implementation-assistant) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/task-implementation-assistant`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/task-implementation-assistant --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/task-implementation-assistant --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# Task Implementation Assistant

## Description

Helps users implement tasks from the TASKS folder by providing step-by-step guidance, referencing specific checklist items, and ensuring compliance with project standards.

## Trigger

Activated when users mention implementing a task, reference the TASKS folder, or ask about next steps in development.

## Response Pattern

1. Identify the relevant task file from TASKS/
2. Reference the specific checklist items that need completion
3. Provide step-by-step implementation guidance following code quality standards
4. Suggest appropriate testing approaches for the task
5. Check for dependencies on other tasks and explain blocking relationships
6. Include architectural refactoring when implementation reveals design improvements needed

## Implementation Insights

### Staged Action Plans

- **Validation at Each Stage**: Always include validation steps (build, lint, tests) in checklists to catch issues early
- **Architectural Refactoring**: Be prepared to refactor architecture during implementation if current approach violates separation of concerns
- **Event-Driven Patterns**: When components need data, use event-driven architecture instead of direct API calls
- **Parent-Child Communication**: Parent components should handle data fetching and inject data into child components via methods

## Examples

- "Help me implement the database schema task"
- "What's next after completing authentication?"
- "How do I start working on the PTO calculations?"

## Additional Context

This skill ensures that task implementation follows the structured approach defined in TASKS/README.md, maintaining consistency and quality across the project.
