skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
olixignacious/agent-skills2 installs

sdlc-feature-dev

Implement an approved TRD — architecture, code, and full test coverage. Requires an approved TRD as input. Spawns api-designer, test-engineer, software-engineer, devops-sre, and technical-writer in sequence. Never starts coding without an approved design.

How do I install this agent skill?

npx skills add https://github.com/olixignacious/agent-skills --skill sdlc-feature-dev
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    The skill is a software development tool designed to automate the process of implementing features from technical requirement documents. It functions as a workflow orchestrator for generating code and tests. While it has filesystem and command-line capabilities, these are within the expected scope for its primary purpose, and no malicious patterns, obfuscation, or unauthorized data access were detected.

  • Socketpass

    No alerts

  • Snykpass

    Risk: LOW · No issues

What does this agent skill do?

Skill: Feature Development

Entry point for Phase 3 of the SDLC workflow.

What This Does

Takes an approved TRD and produces working, tested, documented code ready for review. Tests are written first (TDD). Implementation follows the patterns found by code-archaeologist in the TRD phase. No placeholders, no TODOs, no untested paths.

Input

Provide one of:

  • An approved TRD (from docs/trd/)
  • An approved architectural review + TRD pair
  • A TRD number: "Implement TRD-042"

What Gets Produced

  • Implemented feature code on a feature branch
  • Unit tests (one behavior per test, 80% coverage minimum)
  • Integration tests (real dependencies, no mocks at this layer)
  • E2E tests for the happy path and critical error path
  • API contract spec (if endpoints are added or modified)
  • Deployment plan and runbook (if infrastructure is affected)
  • Updated docs: API docs, ADRs, runbooks

Orchestration

feature-dev-orchestrator
    ├── api-designer       ← contract spec (if API changes in TRD)
    ├── test-engineer      ← failing tests from TRD acceptance criteria
    ├── software-engineer  ← implements against failing tests
    ├── devops-sre         ← deployment plan (if infra changes in TRD)
    └── technical-writer   ← docs, ADRs, runbooks

Next Phase

Implemented + passing tests → /sdlc-code-review

Rules

  • No implementation without a TRD that passed architectural review. If absent, request one.
  • Tests first. Implementation against failing tests only.
  • If a gap is found in the TRD during implementation: stop, document it, return to /sdlc-architectural-review.
  • No // TODO in shipped code.

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/olixignacious/agent-skills/sdlc-feature-dev">View sdlc-feature-dev on skillZs</a>