AgentStack
Sign in Publish
MCP servers Skills Toolkits Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Adlc Architecture

skill-davidvictor-adlc-skills-adlc-architecture · by davidvictor

Create or refresh ADLC architecture artifacts from repo evidence and lifecycle context.

↗ Repository
— No reviews yet
0 installs
3 views
0.0% view→install

Install

$ agentstack add skill-davidvictor-adlc-skills-adlc-architecture

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No 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.

Are you the author of Adlc Architecture? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

ADLC Architecture

Use this when project structure, ownership boundaries, runtime behavior, or major integration decisions need a durable architecture artifact.

Process

  1. Resolve effective ADLC paths from .adlc/config.yaml; use adlc resolve-config when the CLI is available.
  2. Read the configured description, rules, roadmap, interview specs, active plans, and relevant source files.
  3. Identify actual modules, data/control flow, runtime boundaries, agent responsibilities, and integration points.
  4. Use adlc-interview when structural choices require human priorities or decision boundaries before the architecture can be settled.
  5. Update only the configured architecture artifact unless the user asks for broader docs.
  6. Preserve uncertainty as open questions rather than inventing architecture.
  7. Keep diagrams and summaries focused on the system operators actually need to maintain.

Output

Report the architecture artifact path, evidence sources, changed sections, unresolved questions, interview spec path when used, and whether adlc-plan, adlc-docs, or adlc-rules should follow.

Source & license

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

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.

More in Agent Skills