Loading...
Loading...
Found 91 Skills
This skill should be used when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls. Implements Manus-style file-based planning with task_plan.md, findings.md, and progress.md.
Annotate a Spec/PRD with Feature IDs and generate a Coverage Index. Use when user wants to add spec tags to a vision document, create F-nnn identifiers, set up traceability, or initialize a PRD framework for phased development.
Generates professional Statements of Work from a project brief. Use when a user needs to create an SOW, scope a project, define deliverables and milestones, or produce a consulting engagement document.
Execute Preflight phase for /itp:go workflow. TRIGGERS - ADR creation, design spec, MADR format, preflight verification.
When the user wants to create or update a README.md file for a project. Also use when the user says "write readme," "create readme," "document this project," "project documentation," or asks for help with README.md. This skill creates absurdly thorough documentation covering local setup, architecture, and deployment.
Complete Problem-Based Software Requirements Specification methodology following Gorski & Stadzisz research. Use when you need to perform requirements engineering from business problems to functional requirements with full traceability.
Stakeholder Communication (The Diplomat): Prepare context-aware communications (Emails, Updates, Memos) using project data.
Atlassian Template and Files Creator/Modifier expert for creating, modifying, and managing Jira and Confluence templates, blueprints, custom layouts, reusable components, and standardized content structures. Use for building org-wide templates, custom blueprints, page layouts, and automated content generation.
Creates detailed technical specifications for software projects covering requirements, architecture, APIs, and testing strategies. Use when planning features, documenting system design, or creating architecture decision records.
Requirements Analysis SKILL, which can further interact with users to clarify requirements
Use when creating, updating, or generating README and documentation files for projects and libraries
Draft or update requirement documents under `easysdd/requirements/` for the project — describe a capability's "reason for existence, solution approach, and boundaries" using **user stories + plain language**, so non-technical readers can quickly grasp the key highlights of the system. Layered with architecture: requirement is the "problem space" (why this capability is needed), while architecture is the "solution space" (what structure is used to implement it). Two modes: new (draft a new requirement doc from scratch), update (refresh an existing doc based on new materials or implementation changes). Single-target rule — only modify one document at a time. Trigger scenarios: when the user says "fill in a requirement doc", "write down the requirements for this capability", "update the requirements directory", or when it is found during the feature-design phase that there is no corresponding requirement for the capability to be implemented this time.