# Team Discover

> Manually re-scan team context modules and produce a structured discovery table with relevance assessments. The CDR index is already in the system prompt; use this for explicit re-discovery.

- **Type:** Skill
- **Install:** `agentstack add skill-tikalk-adlc-team-skills-team-discover`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [tikalk](https://agentstack.voostack.com/s/tikalk)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [tikalk](https://github.com/tikalk)
- **Source:** https://github.com/tikalk/adlc-team-skills/tree/main/skills/team/team-discover
- **Website:** https://github.com/tikalk/agentic-sdlc-12-factors

## Install

```sh
agentstack add skill-tikalk-adlc-team-skills-team-discover
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# team-discover

## Overview

The CDR index is injected into the system prompt at session start by
team-boot. The LLM natively matches CDR descriptors against the current
task and reads full module bodies on demand. This native matching happens
per prompt without invoking this skill.

Use `/team-discover` when you want a structured discovery table with
explicit relevance assessments — for example, when starting a complex
feature or verifying which directives apply.

## Relationship to team-boot

`team-boot` is the session bootstrap: it injects the CDR index into the
system prompt via the `session_start` event hook. Per-prompt discovery
matching is **native** — the LLM matches the injected CDR index against the
current message on its own, so `team-boot` does **not** invoke this skill
as part of its bootstrap loop.

`/team-discover` is **user-invoked**: run it when you want an explicit,
structured re-scan with a relevance-rated table (complex features, audits, or
verifying which directives apply). It is not required for normal operation.

## Process

1. Extract domain, technology, patterns, and actions from the task.
2. Scan the CDR index for matching entries.
3. Assess relevance: High / Medium / Low.
4. Read full module bodies for High-relevance entries.
5. Output:

| ID | Module | Type | Descriptor | Relevance |
|----|--------|------|------------|-----------|
| CDR-2026-003 | context_modules/personas/admin.md | Persona | Admin persona | High |

6. Include PDR/ADR matches from project indexes if relevant.
7. Include: `_Searched N CDR entries, M PDR entries, K ADR entries, J matches found._`

## Unconfigured projects

If team AI directives are not configured, invoke `team-setup`.

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [tikalk](https://github.com/tikalk)
- **Source:** [tikalk/adlc-team-skills](https://github.com/tikalk/adlc-team-skills)
- **License:** MIT
- **Homepage:** https://github.com/tikalk/agentic-sdlc-12-factors

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-tikalk-adlc-team-skills-team-discover
- Seller: https://agentstack.voostack.com/s/tikalk
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.