[vitormattos]

Summary

Explain how contributors can assess whether an issue is ready to start, especially when it carries the good first issue label.

• Link the good first issue phrase to the organization-wide list of open newcomer tasks.
• Follow native Blocked by dependencies, including chains of prerequisites.
• Check assignees, comments and related pull requests on the issue and blockers, not just the assignment field.
• Offer to contribute to an available prerequisite or select another task when work is blocked or already underway.
• Encourage short coordination comments without treating advance approval as mandatory.

This expands the existing Choose and understand the work section rather than creating a new documentation page.

Companion application PR: LibreSign/libresign#9165 (keeps CONTRIBUTING.md concise and links to this page).

Validation

• Reviewed the diff: only developer_manual/development-workflow.rst was changed.
• Verified that the commit is cryptographically signed and has a matching DCO sign-off.
• GitHub's Documentation workflow passed, including the warning-as-error Sphinx build of the Developer Manual. DCO check passed.

Checklist

• Canonical Developer Manual updated in the existing section.
• No application code or generated Sphinx output changed.
• DCO and signed commit verified.
• AI-assisted documentation disclosed.