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.
Install
$ agentstack add skill-tikalk-adlc-team-skills-team-discover ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-tikalk-adlc-team-skills-team-discover) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →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
- Extract domain, technology, patterns, and actions from the task.
- Scan the CDR index for matching entries.
- Assess relevance: High / Medium / Low.
- Read full module bodies for High-relevance entries.
- Output:
| ID | Module | Type | Descriptor | Relevance | |----|--------|------|------------|-----------| | CDR-2026-003 | context_modules/personas/admin.md | Persona | Admin persona | High |
- Include PDR/ADR matches from project indexes if relevant.
- 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
- Source: 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.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.