Skip to content
Back to skills

659 Description Skill 89da8c2e

ASecurity

Start or complete a specific task inside a SAM task file. Updates task status to IN PROGRESS with Started timestamp, writes active-task context for hooks, and supports --complete to mark tasks complete.

  • 9 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 11, 2026
toolspythonbash

Security analysis

A100/100

Scanned October 11, 2026

npx -y skills add tools-only/X-Skills --skill 659-description-skill_89da8c2e --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of 659 Description Skill 89da8c2e?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for 659 Description Skill 89da8c2e
[![Security: A β€” Skills Directory](https://www.skillsdirectory.com/api/skills/tools-only-659-description-skill-89da8c2e/badge)](https://www.skillsdirectory.com/skills/tools-only-659-description-skill-89da8c2e)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

SKILL.md
---
description: Start or complete a specific task inside a SAM task file. Updates task status to IN PROGRESS with Started timestamp, writes active-task context for hooks, and supports --complete to mark tasks complete.
argument-hint: <task-file-path> [--task <task-id>] [--complete <task-id>]
user-invocable: true
hooks:
  PostToolUse:
  - matcher: Write|Edit|Bash
    hooks:
    - type: command
      command: python3 "${CLAUDE_PLUGIN_ROOT}/skills/implementation-manager/scripts/task_status_hook.py"
version: 1.0.0
last_updated: '2026-01-27'
python_compatibility: 3.11+
---

# Start Task (SAM Task Execution Helper)

You are implementing a specific task from a SAM task file.

<task_input>
$ARGUMENTS
</task_input>

---

## Parse Arguments

- `task_file_path` (required): path to a `plan/tasks-*.md` file
- `--task <id>` (optional): Task ID to start (defaults to first ready task)
- `--complete <id>` (optional): Task ID to mark COMPLETE

---

## Detect Task Format

Read the task file. Determine the format:

- **YAML frontmatter**: File starts with `---` and contains YAML fields like `task:`, `status:`, `title:`
- **Individual task file**: A single file with YAML frontmatter representing ONE task
- **Inline markdown**: File contains `## Task N:` headers with `**Status**:` bold fields

For individual task files (YAML frontmatter at top), the task IS the entire file.
For monolithic files (multiple tasks), find the specific task section.

---

## If `--complete <task-id>` Provided

1. Read the task file.
2. Update the selected task:

   **If YAML frontmatter format:**
   - Edit `status:` field to `complete`
   - Add `completed: {ISO timestamp}` field

   **If inline markdown format:**
   - Change `**Status**` to `βœ… COMPLETE`
   - Add/update `**Completed**: {ISO timestamp}`

3. Output: `Task {ID} marked as complete`

---

## Starting a Task

1. Read the task file and the linked architecture spec.
2. Select the task:
   - If `--task` provided, use that ID
   - Else pick the first task where status is `not-started` (YAML) or `NOT STARTED` (markdown) and all dependencies are resolved
3. Update the task status:

   **If YAML frontmatter format:**
   - Edit the `status:` field in frontmatter to `in-progress`
   - Add `started: {ISO timestamp}` field to frontmatter

   **If inline markdown format:**
   - Set `**Status**: πŸ”„ IN PROGRESS`
   - Add `**Started**: {ISO timestamp}`

4. Write the active-task context file (required for hook-driven updates):

```bash
mkdir -p .claude/context
printf '%s' '{"task_file_path": "{task_file_path}", "task_id": "{task_id}"}' > ".claude/context/active-task-${CLAUDE_SESSION_ID}.json"
```

5. Implement against the task acceptance criteria and run its verification steps.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…