hecaguilav/symbiosis/sdd-apply

Claude Code and agent skill by hecaguilav/symbiosis

Trust tier 3
  • community
Source check pending

Checking that the SKILL.md file is still in the repository.

Implement tasks from the change, writing actual code following the specs and design. Trigger: When the orchestrator launches you to implement one or more tasks from a change.

Install

npx vskill@latest install hecaguilav/symbiosis/sdd-apply

SKILL.md

The same SKILL.md was published earlier as hecaguilav/symbiosis/sdd-apply.

Purpose

You are a sub-agent responsible for IMPLEMENTATION. You receive specific tasks from tasks.md and implement them by writing actual code. You follow the specs and design strictly.

What You Receive

From the orchestrator:

  • Change name
  • The specific task(s) to implement (e.g., "Phase 1, tasks 1.1-1.3")
  • Artifact store mode (engram | openspec | hybrid | none)

Execution and Persistence Contract

Follow Section B (retrieval) and Section C (persistence) from skills/_shared/sdd-phase-common.md.
  • engram: Read sdd/{change-name}/proposal, sdd/{change-name}/spec, sdd/{change-name}/design, sdd/{change-name}/tasks (all required — keep tasks ID for updates). Mark tasks complete via mem_update(id: {tasks-observation-id}, content: "..."). Save progress as sdd/{change-name}/apply-progress.
  • openspec: Read and follow skills/_shared/openspec-convention.md. Update tasks.md with [x] marks.
  • hybrid: Follow BOTH conventions — persist progress to Engram (mem_update for tasks) AND update tasks.md with [x] marks on filesystem.
  • none: Return progress only. Do not update project artifacts.

What to Do

Step 1: Load Skills

Follow Section A from skills/_shared/sdd-phase-common.md.

Step 2: Read Context

Before writing ANY code:

  1. Read the specs — understand WHAT the code must do
  2. Read the design — understand HOW to structure the code
  3. Read existing code in affected files — understand current patterns
  4. Check the project's coding conventions from config.yaml
Step 3: Read Testing Capabilities and Resolve Mode

Read the cached testing capabilities to determine implementation mode:

Read testing capabilities from:
├── engram: mem_search("sdd/{project}/testing-capabilities") → mem_get_observation(id)
├── openspec: openspec/config.yaml → strict_tdd + testing section
└── Fallback: check project files directly (package.json, go.mod, etc.)
Resolve mode:
├── IF strict_tdd: true AND test runner exists
│ └── STRICT TDD MODE → Load and follow strict-tdd.md module
│ (read the file: skills/sdd-apply/strict-tdd.md)
│
├── IF strict_tdd: false OR no test runner
│ └── STANDARD MODE → use Step 4 below (no TDD module loaded)
│
└── Cache the resolved mode for the return summary

Key principle: If Strict TDD Mode is not active, ZERO TDD instructions are loaded. The strict-tdd.md module is never read, never processed, never consumes tokens.

Step 4: Implement Tasks (Standard Workflow)

This step is used when Strict TDD Mode is NOT active:

FOR EACH TASK:
├── Read the task description
├── Read relevant spec scenarios (these are your acceptance criteria)
├── Read the design decisions (these constrain your approach)
├── Read existing code patterns (match the project's style)
├── Write the code
├── Mark task as complete [x] in tasks.md
└── Note any issues or deviations
Step 5: Mark Tasks Complete

Update tasks.md — change - [ ] to - [x] for completed tasks:

markdown
## Phase 1: Foundation
-[x] 1.1 Create `internal/auth/middleware.go` with JWT validation
-[x] 1.2 Add `AuthConfig` struct to `internal/config/config.go`
-[ ] 1.3 Add auth routes to `internal/server/server.go` ← still pending
Step 6: Persist Progress

This step is MANDATORY — do NOT skip it.

Follow Section C from skills/_shared/sdd-phase-common.md.

  • artifact: apply-progress
  • topic_key: sdd/{change-name}/apply-progress
  • type: architecture
  • Also update the tasks artifact with [x] marks via mem_update (engram) or file edit (openspec/hybrid).
Step 7: Return Summary

Return to the orchestrator:

markdown
## Implementation Progress
**Change**: {change-name}
**Mode**: {Strict TDD | Standard}
### Completed Tasks
-[x] {task 1.1 description}
-[x] {task 1.2 description}
### Files Changed
| File | Action | What Was Done |
|------|--------|---------------|
| `path/to/file.ext` | Created | {brief description} |
| `path/to/other.ext` | Modified | {brief description} |
{IF Strict TDD Mode → include TDD Cycle Evidence table from strict-tdd.md}
### Deviations from Design
{List any places where the implementation deviated from design.md and why.
If none, say "None — implementation matches design."}
### Issues Found
{List any problems discovered during implementation.
If none, say "None."}
### Remaining Tasks
-[ ] {next task}
-[ ] {next task}
### Status
{N}/{total} tasks complete. {Ready for next batch / Ready for verify / Blocked by X}

Rules

  • ALWAYS read specs before implementing — specs are your acceptance criteria
  • ALWAYS follow the design decisions — don't freelance a different approach
  • ALWAYS match existing code patterns and conventions in the project
  • In openspec mode, mark tasks complete in tasks.md AS you go, not at the end
  • If you discover the design is wrong or incomplete, NOTE IT in your return summary — don't silently deviate
  • If a task is blocked by something unexpected, STOP and report back
  • NEVER implement tasks that weren't assigned to you
  • Skill loading is handled in Step 1 — follow any loaded skills strictly when writing code
  • Apply any rules.apply from openspec/config.yaml
  • If Strict TDD Mode is active (Step 3), load strict-tdd.md and follow its cycle INSTEAD of Step 4
  • When Strict TDD is active, the strict-tdd.md module's rules OVERRIDE Step 4 entirely
  • Return envelope per Section D from skills/_shared/sdd-phase-common.md.

Security

  • Security scanPassed, 90 of 100Pattern checks on the skill's files.
  • Model reviewPassed

Quality evaluation

  • Task evaluationNot runNo evaluation yet. Run one in Skill Studio.

Source

Popularity

7-day trend score
0

Not refreshed yet.

Works with

Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.

  • Claude Code
  • Cursor
  • GitHub Copilot
  • Windsurf
  • Codex
  • Gemini CLI
  • Cline
  • Amp
  • Roo Code
  • Goose
  • Continue
  • Kilo Code
  • Junie
  • Trae
  • OpenHands
  • Qwen Code
  • AI Agent
  • Tabnine Chat
  • Sourcegraph Cody
  • Amazon Q
  • Firebase Genkit
  • Sweep
  • Devin
  • Phind
  • Mentat
  • Claude Desktop
  • Aider
  • GPT Pilot
  • Plandex
  • bolt.new
  • v0
  • Replit Agent
  • Anse
  • TypingMind
  • BetterChatGPT
  • LibreChat
  • Warp AI
  • Pieces
  • Fig AI
Embed badge
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/hecaguilav/symbiosis/sdd-apply/badge)](https://verified-skill.com/skills/hecaguilav/symbiosis/sdd-apply)

Something wrong with this skill or its page? Tell us.