# Casement Subtask

> Create Casement Jira subtasks under a parent task based on actual git history. Trigger when user asks to: create subtasks, log work to Casement, fill in Casement tasks, add subtasks under a Jira key (e.g. SPSK-XXXXX), plan weekly work items in Casement, or record development work as Casement subtasks. Uses bb-browser site adapters to interact with Casement R&D Platform (casement.scredit.io).

- Skill: `aahowe/casement-subtask` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add aahowe/casement-subtask`
- Raw SKILL.md: https://api.skillmd.com/api/skills/aahowe/casement-subtask/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: aahowe (https://skillmd.com/u/aahowe)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/aahowe/casement-subtask

---


# Casement Subtask Creator

Create subtasks under a parent Jira task in Casement, derived from actual git commit history.

## Workflow

### 1. Gather inputs

Require from user (ask if not provided):
- **Parent Jira key** (e.g. `SPSK-258153`)
- **Date range** or week specification (e.g. "this week 3.30-4.3", "next week 4.7-4.10")
- **Source paths** in repo to scan for commits (default: infer from project context)
- **Assignee** (default: `wanghao`)
- **Task theme/focus** (optional, e.g. "loom local client", "remote execution")

### 2. Check existing subtasks

Fetch current subtasks to avoid duplicates:

```bash
bb-browser site casement/subtasks all --json
```

Note existing summaries and date ranges under the parent key.

### 3. Scan git history

Find commits in the target date range:

```bash
git log --oneline --since="<start-date>" --until="<end-date>" --all -- <paths>
```

### 4. Group commits into subtasks

- Group related commits into logical units of work (1-3 days each).
- Each subtask = one coherent feature, fix, or improvement.
- `storyPoints`: 1 day = 1 SP, 2 days = 2 SP, 3 days = 3 SP.
- Date ranges: contiguous, non-overlapping, skip weekends.
- No overlap with existing subtasks.

### 5. Create subtasks

```bash
bb-browser site casement/create-subtask <parentJiraKey> '{"summary":"[BE] <title>","assignee":"<user>","requirementType":"Coding","phase":"Dev","startDate":"YYYY-MM-DD","dueDate":"YYYY-MM-DD","storyPoints":<n>,"description":"<scope>"}' --json
```

Format rules:
- **summary**: `[BE] <imperative verb phrase>` — all English, concise
- **requirementType**: `Coding` (default)
- **phase**: `Dev`
- **description**: 1-2 sentences describing scope
- **assignee**: username without `@shopee.com` (auto-resolves)

Create all subtasks in parallel when possible.

### 6. Report results

Output a summary table:

| Jira Key | Summary | Date | SP |
|----------|---------|------|----|

## Adapter Reference

See [references/casement-adapters.md](references/casement-adapters.md) for all bb-browser Casement commands.