modular-architecture-documentation-success-criteria
Sub-skill of modular-architecture-documentation: Success Criteria.
Best use case
modular-architecture-documentation-success-criteria is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Sub-skill of modular-architecture-documentation: Success Criteria.
Teams using modular-architecture-documentation-success-criteria should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/success-criteria/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How modular-architecture-documentation-success-criteria Compares
| Feature / Agent | modular-architecture-documentation-success-criteria | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Sub-skill of modular-architecture-documentation: Success Criteria.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Success Criteria ## Success Criteria ✅ **Modular Architecture Documented When:** - [ ] Module structure section in tech-stack.md - [ ] Each module has clear purpose, scope, CLI command - [ ] Shared components identified and justified - [ ] CLI commands documented with examples - [ ] pyproject.toml entry points configured - [ ] Module independence verified (can run standalone) - [ ] Architecture decision recorded in decisions.md - [ ] Testing strategy defined per module - [ ] Adoption path documented (Phase 1, 2, 3) - [ ] Directory structure reflects modular organization ---
Related Skills
improve-codebase-architecture
Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
label-driven-prompt-generation-architecture
Pattern for building automation scripts that classify GitHub issues into prompt templates using label-based routing and extract contextual data for batch processing
documentation-contract-plan-hardening
Harden a documentation/contract plan before adversarial review by mapping every issue-scope requirement to independent acceptance criteria and tests, especially for routing/indexing contracts.
repo-architecture-analysis
Scan a Python repo's package structure, count classes/functions, classify module maturity (PRODUCTION/DEVELOPMENT/SKELETON/GAP), and generate architecture reports with Mermaid diagrams. Use when asked to analyze codebase structure, find untested packages, or assess module maturity.
orcaflex-monolithic-to-modular
Convert monolithic OrcaFlex models (.dat/.yml) to spec-driven modular format with semantic validation for round-trip fidelity.
doc-extraction-naval-architecture
Layer 3 domain sub-skill for extracting naval architecture data from SNAME PNA, IMO stability codes, IACS structural rules, and classification society guidelines. Provides detection heuristics for stability constants, resistance equations, hull form coefficients, hydrostatic curves, IMO stability criteria, and structural scantling tables. type: reference
sparc-architecture
SPARC Architecture phase specialist for system design, component architecture, interface design, scalability planning, and technology selection
architecture-diagram
Dark-themed SVG architecture/cloud/infra diagrams as HTML.
multi-tool-architecture-assessment
Systematic comparison of competing tools/approaches before committing to a multi-account, multi-tool architecture. Uses parallel subagents for research, system-state audit, and data quality analysis. Produces a decision matrix with explicit trade-offs.
modular-architecture-documentation
Systematically document multi-module system architectures including module boundaries, CLI commands, and architecture decisions.
discipline-refactor-orchestration-architecture
Sub-skill of discipline-refactor: Orchestration Architecture.
mkdocs-success
MkDocs success admonition syntax. Use when indicating completed actions or successful outcomes in MkDocs documentation.