complexity-analysis Skill
Complexity analysis for user stories with known work, risks, and scenarios. Use when you need to estimate effort, points, size, or analyze complexity of a user story. Do not use for sprint estimates (use devsquad.sprint) or for artifact quality validation (use quality-gate). Published by microsoft in devsquad-copilot.
What is complexity-analysis Skill?
Complexity analysis for user stories with known work, risks, and scenarios. Use when you need to estimate effort, points, size, or analyze complexity of a user story. Do not use for sprint estimates (use devsquad.sprint) or for artifact quality validation (use quality-gate). Published by microsoft in devsquad-copilot. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Testing
- Data analysis
- Testing use cases
- Data analysis use cases
Technical details
- Install or run with Copy skill directory
When to use complexity-analysis Skill
- Use it for testing.
- Use it for data analysis.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/devsquad-copilot
- Skill file: .github/plugins/devsquad/skills/complexity-analysis/SKILL.md
What it does
Complexity analysis for user stories with known work, risks, and scenarios. Use when you need to estimate effort, points, size, or analyze complexity of a user story. Do not use for sprint estimates (use devsquad.sprint) or for artifact quality validation (use quality-gate).
Skill instructions
Principle Focus on the unknowns, not the knowns. Unknown work dominates software projects. Evidence Rule Every classification (known/unknown) must cite the evidence that supports it. Reference code, ADR, spec, or absence thereof. If uncertain, say so and indicate what information would resolve the uncertainty. Analysis Structure 1. Known Work Tasks whose effort can be estimated with confidence: - We have done something similar in this project - Established pattern in ADR or existing code - Well-defined scope in the spec - Existing test coverage in the affected area - Localized change (few impacted dependencies) For each item, indicate why it is known (e.g., "CRUD endpoint, same pattern as src/api/users"). 2. Unknown Work (Risks) Signals of uncertainty: - First time (new technology, integration, or pattern) - External dependency (third-party API, another team's service) - Vague requirement ("must be fast", "easy to use") - Pending decision (no ADR exists for technical choice) - Legacy c
Explore related resources
Frequently asked questions
What is complexity-analysis?
complexity-analysis is a open-source AI agent skill with Copy skill directory. Complexity analysis for user stories with known work, risks, and scenarios. Use when you need to estimate effort, points, size, or analyze complexity of a user story.
Who is complexity-analysis best for?
complexity-analysis is best for reusing agent instructions, scripts, and references, testing workflows, data analysis workflows.
How do I install complexity-analysis?
Install or run complexity-analysis using Copy skill directory. Check complexity-analysis for the latest setup command.
Is complexity-analysis actively maintained?
complexity-analysis may need a closer maintenance check before production use.
Auto-fetched from GitHub.
