Implement Python code. Invoke for Python-language implementation tasks.
Thin wrapper that delegates Python implementation to python-implementation-agent subagent.
This skill activates when:
Validate task_number exists and language is "python".
Update status to "implementing" BEFORE invoking subagent.
Include task_context, plan_path, metadata_file_path.
Use Task tool with subagent_type: "python-implementation-agent".
CRITICAL: If you performed the work above WITHOUT using the Task tool (i.e., you read files,
wrote artifacts, or updated metadata directly instead of spawning a subagent), you MUST write a
.return-meta.json file now before proceeding to postflight. Use the schema from
return-metadata-file.md with the appropriate status value for this operation.
If you DID use the Task tool, skip this stage -- the subagent already wrote the metadata.
The following stages MUST execute after work is complete, whether the work was done by a subagent or inline (Stage 4b). Do NOT skip these stages for any reason.
Read the metadata file from specs/{N}_{SLUG}/.return-meta.json.
Update state.json and TODO.md based on result.
Add artifact to state.json with summary. Update TODO.md per @.claude/context/patterns/artifact-linking-todo.md with field_name=**Summary**, next_field=**Description**.
Commit changes with session ID.
After the agent returns, this skill MUST NOT:
PROHIBITION: If the subagent returned partial or failed status, the lead skill MUST NOT attempt to continue, complete, or "fill in" the subagent's work. Report the partial/failed status and let the user re-run
/implementto resume.
The postflight phase is LIMITED TO:
Reference: @.claude/context/standards/postflight-tool-restrictions.md
Brief text summary (NOT JSON).