Magnus Hedemarkandfactory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
c0c7690724
Move the 8 directories under bundles/ to the repo root via git mv and remove the now-empty bundles/ directory. Replace the "bundles" entry in pyproject.toml [tool.deptry] extend_exclude with the 8 moved dir names so the moved trees stay excluded from Python dependency analysis. Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
2.1 KiB
name, description, license, compatibility, metadata
| name | description | license | compatibility | metadata | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| deep-work | Use when the user shifts into focused building or research mode — writing code, drafting content, implementing a feature, researching a topic, or designing. Activates after triage or when the session opens with a task. | MIT | Compatible with any agent supporting the Agent Skills format |
|
Deep Work
This skill is part of the developer-triage bundle, generated by workflow-architect on 2026-05-29.
When to Use
Activate when the user commits to a specific deliverable or task. Signals include: naming a file or feature to build, asking for implementation help, requesting research on a topic, or saying "let's work on X."
What to Do
-
Clarify the goal. What exactly is being built, written, or researched? Get a one-sentence definition of done before starting.
-
Gather context. Load relevant files, documentation, or previous work. Present a brief status: what already exists, what needs to change.
-
Work iteratively. Build or research in small cycles. After each cycle, summarize what was done and confirm the user wants to continue before moving to the next step.
-
Handle interruptions. If the user context-switches during deep work, save the current state and note what was in progress before switching.
Transition Signals
This phase ends when the user either:
- Completes the deliverable ("that's it, ship it")
- Hits a state change like needing a PR review before continuing
- Decides to pause and switch to something else
- Runs out of time/energy for this session
What to Tell the User
Match the user's energy. If they're in flow, keep responses minimal and actionable. If they're exploring, offer options and alternatives. Save checkpoint summaries at each notable milestone.
Example:
"The feature branch is up to date. I implemented the core logic in
src/handler.py (82 lines), added tests in tests/test_handler.py (34 lines),
and everything passes. Want me to push and open a PR?"