Repository profile

adlc-team-skills

Review Skills in tikalk/adlc-team-skills, with license, maintenance context, and source paths.

Skills
15
Repository stars
97
Identity status
Source-linked

Provenance

Source and identity

Source-linked
Profile type
Repository
Canonical name
adlc-team-skills
Public sources
1
License context
MIT

Source entries

Agent Skills from adlc-team-skills

Repository stars and maintenance signals provide context, but do not automatically become an individual Skill's quality score.

Computed 9697

tikalk/adlc-team-skills

architect-analyze

Analyze architecture for consistency between ADRs and AD, completeness, and quality issues. Use when validating generated or refined architecture artifacts, before feature development, during architecture review, or periodically to detect drift.

Computed 9497

tikalk/adlc-team-skills

architect-clarify

Refine and validate system-level ADRs through targeted clarification questions. Use when ADRs need review, gaps need filling, or ADR status must be approved before architecture generation.

Computed 9597

tikalk/adlc-team-skills

architect-implement

Generate a full Architecture Description (AD.md) from accepted ADRs using multi-agent DAG orchestration. Use when accepted ADRs exist and you need to produce or update unified architecture documentation.

Computed 9197

tikalk/adlc-team-skills

architect-init

Reverse-engineer architecture from an existing codebase to create ADRs documenting discovered decisions. Use when bootstrapping architecture documentation for brownfield projects.

Computed 8897

tikalk/adlc-team-skills

architect-specify

Interactive PRD exploration and system-level ADR creation for greenfield projects. Use when transforming a PRD or high-level system description into Architecture Decision Records.

Computed 8897

tikalk/adlc-team-skills

evals-init

Initialize evals/{system}/ directory structure for evaluation system following EDD principles (Standalone). Choose PromptFoo or DeepEval based on tech stack, generate security baseline.

Computed 8997

tikalk/adlc-team-skills

levelup-clarify

Review, accept, reject, or defer Context Directive Records (CDRs) discovered by levelup-init or proposed by levelup-specify. Interactive one-CDR-at-a-time workflow.

Computed 8997

tikalk/adlc-team-skills

levelup-publish

Compile accepted Context Directive Records (CDRs) into team-ai-directives artifacts and create a draft PR. Builds context modules, evals goldensets, and/or skills based on CDR context types.

Computed 9497

tikalk/adlc-team-skills

mission-brief

Mission-driven SDD orchestrator: take a feature description, structure it into a Mission Brief (goal, constraints, success criteria), generate an ordered step list with prompts that trigger installed SDD skills via model invocation or command-file discovery, and walk those steps to converged implementation. Use when you want an end-to-end specify → plan → implement ↔ converge loop with gates, a circuit breaker, resume, and an audit trail — without YAML files or per-framework profiles.

Computed 9297

tikalk/adlc-team-skills

product-implement

Generate a full Product Requirements Document (PRD.md) from accepted PDRs using multi-agent DAG orchestration. Reads individual PDR files, generates PRD sections from templates, validates output, and promotes accepted PDRs to memory. Use after /product.clarify.

Computed 9197

tikalk/adlc-team-skills

product-specify

Interactive PRD exploration and Product Decision Record (PDR) creation for greenfield products. Facilitates product discovery discussions, surfaces trade-offs, and documents decisions as individual PDR files. Use when starting a new product or major pivot.

Computed 9097

tikalk/adlc-team-skills

team-constitution

Interactively create or amend the team constitution in team-ai-directives. Use when bootstrapping a new team AI directives, establishing team-wide principles for the first time, or amending existing ones.

Pinned paths

Every entry links to a specific source path and commit when available.

Repository context

Activity, license, and repository-level popularity are shown as context.

Open the source

Inspect the public repository