One-click install
npx skills add https://github.com/kryptonum-dev/fabryka-atrakcji --skill 10x-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 10x-plan
Source: https://github.com/kryptonum-dev/fabryka-atrakcji/tree/main/.agents/skills/10x-plan
Command: npx skills add https://github.com/kryptonum-dev/fabryka-atrakcji --skill 10x-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps convert a task or ticket into a thorough, implementation-ready plan by gathering context, researching the codebase, and iterating with you to make the key decisions.

Core Features & Use Cases

  • Iterative planning with questioning: Asks targeted questions at the right depth, avoiding rework when frame briefs or research already exist.
  • Context-aware research workflow: Reads provided artifacts fully, then performs guided discovery (via sub-tasks) to ground the plan in real existing patterns.
  • Production-quality plan output: Produces a structured plan.md with phases, clear contracts, success criteria, and a single mechanical ## Progress section.
  • Plan brief generation: Writes a concise two-pager (plan-brief.md) to help readers quickly understand scope, starting point, end state, and key decisions.

Quick Start

Use 10x-plan with your task description or by referencing a frame/research file, for example: /10x-plan oauth-login.

Frequently Asked Questions about 10x-plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn a vague software ticket into a detailed implementation plan?

To create a detailed implementation plan, gather task context and research the codebase to iteratively confirm key decisions. This process converts vague tickets into phased execution plans with explicit contracts, success criteria, and a mechanical progress tracking section.

What is the best way to structure technical specifications for a new feature?

Structuring technical specifications requires applying iterative questioning and codebase research to ground the design in existing patterns. The output is a structured plan with phased execution, explicit contracts, and success criteria to guide development.

How do I create an implementation-ready plan without redundant questioning?

To avoid redundant questioning during implementation planning, read provided frame briefs and research artifacts fully before asking targeted questions. This respects existing context and prevents unnecessary rework when establishing technical specifications.

Can I generate a quick summary of a software build plan alongside the full technical specifications?

Yes, alongside the full implementation plan, you can generate a concise plan brief. This two-page summary helps readers quickly understand the scope, starting point, end state, and key decisions without reading the entire technical specification.

Does implementation planning work for process work or only software engineering tasks?

Implementation planning applies to both software and process work. As long as the deliverable requires phased execution, explicit contracts, success criteria, and a canonical progress tracking section, the planning process will structure the task effectively.

How do I track progress mechanically once an implementation plan is in place?

Track progress mechanically by maintaining a single canonical Progress section within the generated plan. This section provides a structured, ongoing record of phased execution milestones derived from the initial technical specifications and codebase research.