Loading...
Loading...
Found 8 Skills
Display project status, active tracks, and next actions
Generates a full comprehensive status update of the project. Use when the user asks for a status update, progress report, "STATUS UPDATE", "WHAT'S THE STATUS", or wants to know what's done, what's broken, and what's next. Writes to docs/status/.
Socratic questioning protocol + user communication. MANDATORY for complex requests, new features, or unclear requirements. Includes progress reporting and error handling.
Execute an approved implementation plan in a separate session with checkpoint reviews. Use after writing-plans when the user wants batched progress updates before more work continues.
Generates reports by aggregating project progress by status, priority, and size. A read-only skill that outputs completion rates and breakdowns of incomplete items by priority in tabular format. Use with commands like "Show progress", "Project report", "What's the completion rate?", "Number of items by status".
Use during active user/operator-facing work to keep agent interaction actionable: retain agent-owned work, expose verified state and blockers, ask only necessary questions, bound required user actions, suppress tangents, and report errors with evidence and a concrete recovery path.
Summarize the current task's progress and blockers.
Use for coding-agent conversation communication across any project or task: explain the current task and outcome, report progress, maintain the complete plan, present decisions or blockers, and resume or hand off long work. Applies alongside coding, design, research and writing skills without requiring Agently. Brief factual answers stay brief; application runtime progress and deliverable design remain with their task owners.