Provide blunt critique on counting, estimation, and architecture decisions.
npx skills add https://github.com/milistu/agent-skills --skill challenge-me
Please help me install this Agent Skill. Skill: challenge-me Source: https://github.com/milistu/agent-skills/tree/main/skills/challenge-me Command: npx skills add https://github.com/milistu/agent-skills --skill challenge-me
This skill provides blunt, specific critique and concrete guidance for counting, estimation, and architecture/design decisions, helping teams identify hidden work and hard tradeoffs early.
Initiate challenge-me mode and ask for blunt, actionable critique on your counting, estimates, and design approach.
High-intent search queries and answers about installing and using this skill.
To get concrete critique on software architecture decisions and estimates, use a blunt advisory tool that enforces explicit assumptions and surfaces hidden work. This approach identifies edge cases, rollback implications, and security risks early in the design phase.
The best way to surface hidden risks during early project scoping is to apply blunt, no-nonsense critique focused on correctness and maintainability. This enforces explicit assumptions and counts edge cases, migrations, and performance implications.
To ensure accurate engineering estimates for complex design reviews, apply blunt critique that counts edge cases and enforces guardrails for maintainable design. This surfaces blind spots and enforces a clearer definition of done.
Yes, you can use blunt critique to identify missing observability and rollback plans in your architecture. This advisory approach counts these specific implications during design reviews to surface hard tradeoffs and enforce guardrails.
You need explicit assumptions and edge case counting for maintainable design during early scoping, architecture workshops, and design reviews. This process surfaces blind spots, enforces clearer scope, and ensures accurate project estimates.
Blunt critique helps with counting edge cases and migration risks in software engineering by providing direct, no-nonsense feedback focused on simplicity. It surfaces hidden work and hard tradeoffs early, enforcing explicit guardrails for maintainable design.
patrickrmooreDraft and maintain a project-level Software Architecture Document in specs/sad.md.
niltonfredericoConvert validated Monday.com analysis into implementation plans with Planning Poker estimates.
lucascaroDetect and correct code deviations against golden-principle guidelines in repositories.
MOODMNKY-LLCCreate SVG or Excalidraw diagrams for concepts, architecture, and processes.
