// Start an implementation task with proper planning, TDD workflow, and session hand-off. Use when beginning work on a Jira issue, starting a new feature, or resuming implementation work. Triggers on phrases like "start task", "begin implementation", "work on issue", or "implement feature".
Prepare and commit code changes with full verification, pre-commit checks, and tests. Runs verification skill, fixes issues using TDD, executes all test suites, and creates atomic commits. Use when ready to commit changes, before committing, or when asked to prepare a commit.
Create structured implementation plans for Jira issues using the project template. Use when starting a new task, implementing a feature, when asked to create a plan, or when the implementation skill detects no existing plan.
Deep verification of code changes before committing. Traces code paths, detects semantic changes, identifies code smells and security issues. Reads GitHub PR reviews to propose implementation decisions. Use before commits, after implementation, or when asked to verify/review changes.
Deep verification of code changes before committing. Traces code paths, detects semantic changes, identifies code smells and security issues. Reads GitHub PR reviews to propose implementation decisions. Use before commits, after implementation, or when asked to verify/review changes.
| name | implementation |
| description | Start an implementation task with proper planning, TDD workflow, and session hand-off. Use when beginning work on a Jira issue, starting a new feature, or resuming implementation work. Triggers on phrases like "start task", "begin implementation", "work on issue", or "implement feature". |
Check Plan → [Create if missing] → TEST FIRST → Implement → Test & Lint → Commit → Session Hand-off
TDD is NON-NEGOTIABLE: Every code change requires a failing test BEFORE implementation.
# Extract issue ID from branch
git branch --show-current
The issueID follows format XXX-XXXX (e.g., IDE-1718).
Look for: ${issueID}_implementation_plan/${issueID}_implementation_plan.md
If plan exists: Read it, note current progress, continue from last checkpoint.
If no plan: use skill create-implementation-plan to create one
See: docs/diagrams/${issueID}_*.png
** read and use testing skill for TDD instructions **
./gradlew test)./gradlew verifyPlugin)./gradlew ktlintCheck spotlessApply)| Step | Status | Notes |
|---|---|---|
| Step 1 | pending |
Started: [time] Completed: [list of completed items] Next: [next steps for hand-off]
Create mermaid files ${issueID}_*.mmd
Stop here. Present the plan and wait for user confirmation before proceeding.
NEVER write production code before writing a failing test.
This applies to:
** ALWAYS use the testing skill. **
Before writing ANY production code, verify:
If ANY answer is NO → STOP and write the test first.
For each feature/change:
# Run unit tests
./gradlew test
# Run smoke tests
./gradlew verifyPlugin
# Format and lint
./gradlew ktlintCheck spotlessApply
Before each step:
## Progress Tracking
| Step 1 | **in-progress** | Started [time] |
After each step:
## Progress Tracking
| Step 1 | **completed** | Finished [time] |
./gradlew test
INTEG_TESTS=1 ./gradlew test
./gradlew verifyPlugin
All tests must pass. Fix any failures before proceeding.
./gradlew ktlintCheck spotlessApply
Zero linting errors required. Fix any issues.
Run before commit:
snyk_code_scan with absolute project pathsnyk_sca_scan with absolute project pathFix any security issues (except in test data).
Update documentation in ./docs as needed.
Pre-commit checklist:
Commit format:
type(scope): description [XXX-XXXX]
Body explaining what and why.
Never skip hooks. Never use --no-verify.
Update implementation plan with session summary according to the plan session handoff section.
| Action | Command |
|---|---|
| Unit tests | ./gradlew test |
| Integration tests s | INTEG_TESTS=1 ./gradlew test |
| Smoke tests | ./gradlew verifyPlugin |
| Format & lint | ./gradlew ktlintCheck spotlessApply |